For people who build software with coding agents
ctxflows is the context layer and the workflows for agent-built software.
Context is what your coding agents know: roadmap, boards, docs and the business logic your product follows. Flows are how they work: workflows with nodes, loops and your decisions.
Private beta. Access opens by invitation.
One change, from a goal to what the next session knows
Follow one change through ctxflows: each stage leaves a record the next stage reads, so no agent starts from a blank page.
Start with the outcome you want.
Start with the outcome you want.
The work begins on the roadmap, with what should change and how you will know it worked, before any code is touched.
Roadmap · goal
Make project knowledge easy to find
- Outcome
- Find the project context you need without knowing which page holds it.
- Next milestone
- Project search.
- What done means
- Records and docs are found by title or by meaning, and a reader sees only what they may see.
Carried forward
The next item has a reason to exist and a written definition of done.
Turn the goal into an item on a board.
The item stays linked to its milestone and to the docs it is built from, so its purpose survives every handoff.
Board · item
Add ranked project search
- Serves
- The project search milestone.
- Built from
- The project search requirements page.
- Scope
- Search records and docs together, ordered by relevance.
Carried forward
A bounded item carries its requirements into the agent's session.
Hand the agent the context this task needs.
Before the agent starts, the context step gathers the pages, rules and terms that apply to this item, and nothing more.
Docs · page
Project search requirements
- Product intent
- Search records and docs together. Rank exact title matches first.
- Rule that applies
- Apply what the reader may see before ranking results.
- Checks to include
- Empty results, and records the reader cannot see.
Carried forward
The same written requirements guide the change and the checks it is judged by.
Follow the workflow the item's column starts.
Reaching Ready starts the board's build workflow. Your agent plans, then builds in a loop until the checks pass, on your machine.
Workflow
Build a feature
- Started by
- The item reaching Ready on the Feature board.
- Agent nodes
- Plan, then build and test in a loop until the checks pass.
- Approval
- Review waits for a person before the change lands.
Carried forward
Each node's outputs stay with the item: the plan, the change and the check results.
An approval waits for you.
The run stops at its Review approval. You see the outputs, the check results and the branch, and decide whether the change meets the goal.
Run · waiting on you
Review ranked project search
- Where the run stands
- At the Review approval, with every check passed.
- The question
- Does the change meet what done means for this goal?
- Your answers
- Approve it, or send it back with a note.
Carried forward
Nothing lands until a person approves it, and waiting costs nothing.
Keep what the work taught you.
What a run finds is written back as it works, linked to the item that produced it, so the next session starts from it.
Memory · finding
Apply visibility before ranking
- Learned
- Filtering after ranking can leave empty pages even when visible matches exist.
- Linked to
- The project search item and the run that found it.
- Used next time
- Every new searchable record type follows the same order.
Carried forward
The next session builds on what was recorded, instead of rebuilding the conversation.
Agents are fast. What they can't keep is why.
Coding agents now write most of the code, on your machine or your server. What they can't keep is what the product must do and why. ctxflows is where that lives: roadmap, boards, docs and the rules your product follows, written once, and the workflows agents follow to build from them.
The tools you know, rebuilt for agents
Roadmap, boards, docs, a glossary and workflows work the way you know them, and each is rebuilt so your coding agents read it, follow it and write back to it.
Plan the work
Write it down
Build with agents
Start with your agent, add the engine
Start in your own session with the agent you already use. Add the engine when ready work should keep moving while you're away.
Connect any coding agent over MCP. Install the free engine to run Claude Code, Codex, Cursor, Gemini CLI or Grok unattended, or mix them per task. One set of rules for every agent instead of one per vendor.
What lives where
In ctxflows: roadmap, boards, docs, library, terms, datasets, workflows, runs and the journal of every change. On your machine or server: your code, credentials, agent sessions and transcripts. Export everything as plain files at any time.
- Your code never enters ctxflows.
- A person decides what is built and whether it was met.
- ctxflows runs no coding agent: your code is built by your agents on your machine. The built-in assistant works only on your project's record.
When an agent is wrong
A node can't close until its outputs exist; a check that must pass blocks it; a loop repeats until checks pass; an approval waits for you. Send work back, redo a run or cancel it. An agent the engine started never approves its own work.
Each agent can do only what you allow, and every change is recorded: who made it, when and why.
Software built from written intent
Almost everything the industry built to manage software work makes up for people being slow, opaque and not interchangeable. Agents remove what it made up for.
What remains is your product's business logic: not the code, but what the product must do, for whom and why. ctxflows keeps it written once, where every agent reads it, so written intent becomes the thing software is built from.
ctxflows is built by Dennis Zaiser, technical founder.
Questions about ctxflows
Is this another tracker?
Does ctxflows run my agents?
Which coding agents does ctxflows work with?
Where does my code go?
Can I use ctxflows today?
Can I use it without a terminal?
Give your coding agents the context and the workflows
Plan the work, write it down and build with the agents you already use.