BUILT FOR THE WAY YOU BUILD NOW

Turn ideas into work
for your coding agents.

A home for your next idea. A queue for what comes next.
Prompt Waypoint turns focused prompts into tasks for Codex and Claude—on your own machines.

See how it works Your agents. Your machines. Your direction.
Prompt WaypointWorkspace / DatovkaProduct preview
YOUR NEXT SHIP STARTS HERE

Small tasks. Real progress.

● MacBook Air · Online

Running1

Add Keychain auth

Working in a fresh session

Codex · MacBook Air

Waiting1

Model downloader

Waiting for provider capacity

Claude Code · Desktop

Ready2

Detect available RAM

Ready for a focused run

Codex · MacBook Air

Recommend a model

Prompt saved

Claude Code · Desktop

Inbox2

Multi-account login

An idea for later

Datovka

Improve onboarding

Prompt saved

Datovka
One task. One clear instruction.Inbox → Ready → Queued → Running → Waiting → Done
FROM THOUGHT TO FOLLOW-THROUGHCodex / Claude Code / Desktop + Mobile

LESS SCROLLING. MORE SHIPPING.

Good ideas deserve
more than a chat history.

01

Lost in the conversation

The implementation plan is somewhere in a long chat. Save the useful prompts as tasks you can come back to.

02

Too much in one prompt

Auth, billing and onboarding need room to breathe. Give independent changes a focused task and, when useful, a clean agent session.

03

An agent still needs direction

Decide what runs next. See what finished, what is waiting and what needs your input—all in one workflow.

A SIMPLE LOOP

Think it through. Put it in motion.

Keep the conversation creative and the execution focused.

  1. 01

    Think

    Explore the product or architecture with your preferred AI.

  2. 02

    Capture

    Turn the discussion into focused prompts in your backlog.

  3. 03

    Execute

    Send each task to Codex or Claude on the right machine.

  4. 04

    Monitor

    Follow progress, completion and requests for your input.

  5. 05

    Continue

    Review the result. Give the next step a task of its own.

ONE PLACE TO KEEP WORK MOVING

A little structure.
A lot less juggling.

01 /

A backlog for your prompts

Keep the title, prompt, repository and execution target together. Your next task is ready when you are.

02 /

Codex + Claude Code

Orchestrate the local coding tools you already use, with provider profiles for different setups.

03 /

Desktop + mobile

Plan at your desk. Capture an idea, check progress or answer your agent from your phone.

04 /

More than one machine

Keep repositories grouped by device. Send work to the computer where that project lives.

05 /

A queue with intent

Move from Inbox to Ready, then explicitly Run or Queue. Track running, waiting and completed work.

06 /MCP

Conversation → task

MCP integration lets compatible AI clients turn a discussion into focused backlog items. Creating tasks and starting work stay separate.

07 /

Continue after capacity returns

Resume supported tasks when provider capacity becomes available. Quota data and auto-resume depend on provider capabilities.

08 /Planned · optional

Help choosing how to run

An optional AI Task Router is planned to recommend provider, model tier, reasoning effort and session choice—and flag tasks that are too broad.

LOCAL-FIRST, BY DESIGN

Your coding agents
keep working on
your machines.

Prompt Waypoint coordinates the work. Your development environment stays yours.

Repositories and coding-agent credentials stay on your machines for orchestration. The server syncs task and prompt content, metadata and execution updates, relays commands and sends notifications.

Your coding providers retain their own data handling policies. Local execution does not mean that no data leaves your device.

Mobile app
Desktop app
↕ Task content & status
Prompt Waypoint ServerSync · command relay · push
↕ Commands & execution updates
ON EACH OF YOUR MACHINES
Local Prompt Waypoint Agent
CodexClaude Code
Local repositories
Simplified orchestration flow

A DIFFERENT KIND OF WORK ITEM

Product management when
the developer is an AI agent.

Part requirement. Part work item. An instruction ready to run.

TRADITIONAL TASK TRACKER

Requirement → Ticket → Human developer → Implementation

THE Prompt Waypoint WORKFLOW

Idea → Focused prompt → Coding agent → Result

A task holds the intent. A session is how the agent carries it out.

MCP INTEGRATION

From AI conversation
to backlog.
Without copy-paste.

Keep the ideas flowing. Give the implementation steps somewhere to land.

MCP lets compatible AI clients create and manage tasks directly from a discussion. Saving a task will not, by itself, start a coding agent. Execution remains an explicit decision.

Illustrative MCP workflow
YOU

Split this architecture into four implementation tasks and add them to Prompt Waypoint.

YOUR AI CLIENT

Four focused tasks, ready for your backlog.

  • Create provider abstraction
  • Implement Codex adapter
  • Add Claude adapter
  • Add reconciliation loop
Saved to Inbox · awaiting your direction

AWAY FROM YOUR DESK, STILL IN THE LOOP

The next idea
won’t wait until
you’re back.

Capture it on your phone. Send it to the right machine. Get notified when the work is done.

  • Save a prompt in a few taps
  • Check running and waiting tasks across devices
  • Reply when an agent needs your input
  • Queue, resume or stop work remotely

An offline device can receive new tasks in the backlog. Execution needs the machine to reconnect.

Prompt WaypointM

Your work, in motion.

2Running
1Waiting
8Ready

DEVICES

MacBook Air2 repositories● Online
DGX Spark1 repository● Online
AGENT NEEDS INPUTChoose the sign-in flow

Datovka · Claude Code

Reply and keep things moving ↗
+ New Task
Mobile product preview

A FEW GOOD QUESTIONS

Before you
put it to work.

Does Prompt Waypoint replace Codex or Claude?

No. Prompt Waypoint coordinates the coding agents you already use. The agents do the implementation; Prompt Waypoint keeps the work organized.

Does the code run in the cloud?

Coding-agent processes run on your configured machine against local repositories. Prompt Waypoint syncs task and prompt content, execution updates and metadata through its server. Your coding provider may process code according to its own settings and policies.

Does Prompt Waypoint need GitHub access?

No. The current core workflow uses local repositories and prompt-based tasks. It does not require GitHub or Git integration.

Can I use multiple computers?

Yes. Repositories belong to devices, and one account can manage multiple devices and their provider profiles.

Can AI create tasks automatically?

Compatible MCP clients can create backlog items from conversations using your Prompt Waypoint account token. Creating a task and authorizing its execution are separate decisions. Clients that require OAuth account linking need a future authentication extension.

Is Prompt Waypoint an IDE?

No. It is a task and orchestration layer. Keep using your preferred editor and development environment.

Is it free?

Pricing has not been announced yet.

MAKE ROOM FOR WHAT’S NEXT

Your next idea.
Your agents’ next task.

● Public beta coming soon