Add Keychain auth
Working in a fresh session
BUILT FOR THE WAY YOU BUILD NOW
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.
Working in a fresh session
Waiting for provider capacity
Ready for a focused run
Prompt saved
An idea for later
Prompt saved
LESS SCROLLING. MORE SHIPPING.
The implementation plan is somewhere in a long chat. Save the useful prompts as tasks you can come back to.
Auth, billing and onboarding need room to breathe. Give independent changes a focused task and, when useful, a clean agent session.
Decide what runs next. See what finished, what is waiting and what needs your input—all in one workflow.
A SIMPLE LOOP
Keep the conversation creative and the execution focused.
Explore the product or architecture with your preferred AI.
Turn the discussion into focused prompts in your backlog.
Send each task to Codex or Claude on the right machine.
Follow progress, completion and requests for your input.
Review the result. Give the next step a task of its own.
ONE PLACE TO KEEP WORK MOVING
Keep the title, prompt, repository and execution target together. Your next task is ready when you are.
Orchestrate the local coding tools you already use, with provider profiles for different setups.
Plan at your desk. Capture an idea, check progress or answer your agent from your phone.
Keep repositories grouped by device. Send work to the computer where that project lives.
Move from Inbox to Ready, then explicitly Run or Queue. Track running, waiting and completed work.
MCP integration lets compatible AI clients turn a discussion into focused backlog items. Creating tasks and starting work stay separate.
Resume supported tasks when provider capacity becomes available. Quota data and auto-resume depend on provider capabilities.
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
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.
A DIFFERENT KIND OF WORK ITEM
Part requirement. Part work item. An instruction ready to run.
Requirement → Ticket → Human developer → Implementation
Idea → Focused prompt → Coding agent → Result
A task holds the intent. A session is how the agent carries it out.
MCP INTEGRATION
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.
AWAY FROM YOUR DESK, STILL IN THE LOOP
Capture it on your phone. Send it to the right machine. Get notified when the work is done.
An offline device can receive new tasks in the backlog. Execution needs the machine to reconnect.
Your work, in motion.
Datovka · Claude Code
Reply and keep things moving ↗A FEW GOOD QUESTIONS
No. Prompt Waypoint coordinates the coding agents you already use. The agents do the implementation; Prompt Waypoint keeps the work organized.
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.
No. The current core workflow uses local repositories and prompt-based tasks. It does not require GitHub or Git integration.
Yes. Repositories belong to devices, and one account can manage multiple devices and their provider profiles.
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.
No. It is a task and orchestration layer. Keep using your preferred editor and development environment.
Pricing has not been announced yet.
MAKE ROOM FOR WHAT’S NEXT