Local process control for coding agents

Keep coding agents
on track.

Bound the scope.Cap verification.Resume after interruption.

Keep scope, progress, and recovery state outside the chat.

Get Started View on GitHub

npm install -g @imotong/dev-flow@latest

Dev FlowTask control

LOCAL

TASKFix the login retry bug.

Simplified view

✓REQUIREMENTSREQ
✓DESIGNDES
3IMPLEMENTIMP
4TESTTEST
5DONEDONE

IMPLEMENT

Scope retained

Scope: ✓ packages/auth/**
Verification: 2 targeted checks

01 The problem

Coding agents are powerful.
Long-running coding tasks are messy.

Scope creep

A precise fix quietly becomes permission to improve everything nearby.

Fix this API
Refactor nearby code
Unrelated work

Verification spiral

A targeted check grows into an open-ended search for more confidence.

Targeted test
Full suite
Platform matrix

Lost state

The conversation ends. The next session has to reconstruct what happened.

SESSION 1IMPLEMENT → TEST

context lost

SESSION 2“Let me inspect the repository…”

02 The process

Every next step is explicit.
So is every step back.

Simplified viewstandard-development

✓REQUIREMENTS
✓DESIGN
✓IMPLEMENT
4TEST
5REVIEW
6DONE

TESTIMPLEMENTimplementation gap

REQUIREMENTS
DESIGN
IMPLEMENT
TESTCurrent
REVIEW
DONE

Explore the full workflow

03 What Dev Flow adds

A process your agent
can come back to.

01 / 04

Stay inside the task.

The request, acceptance criteria, and out-of-scope work stay attached to the Task.

Allowed: ✓ packages/auth/**
Acceptance: ✓ lock after 5 failed attempts
Out of scope: × database/** · unrelated refactors

02 / 04

Test enough.Not forever.

A verification budget keeps checks tied to the changed surface and acceptance criteria.

Targeted tests2 checks

Inside the budget

03 / 04

Resume whereyou stopped.

Stage, revision, and evidence persist, so a new session reads the Task instead of guessing.

BEFORE RESTARTTEST

Revision: 5
Evidence: 2 checks

Host restart

AFTER RESTARTTEST

Revision: 5
Evidence: Preserved

04 / 04

Read beforeretrying.

After an uncertain write, read authoritative state before deciding whether to retry.

write
response lost
read authoritative state
decide

04 Control Center

See what your agent
is doing.

A focused local view of the current stage, targeted verification, timeline, and retained evidence.

Dev Flow Control Center

127.0.0.1

← All Tasks

ACTIVE · CODEX

Fix the login retry bug.

task-auth-042

Revision: r5
Updated: just now

CURRENT STAGE

Test

TEST

Verify the current repository behavior within the immutable verification budget.

Verification: targeted2 automatic commands
Revision: 5just now

HISTORY

Timeline

r5IMPLEMENT → TEST

FACTS

Evidence

Acceptance criteria: Lock after 5 failed attempts.
Verification: 2 automatic commands

05 Clear boundaries

Dev Flow doesn’t replace
your coding agent.

EXECUTION

Your agent executes.

Codex / DeepSeek

Read
Edit
Run
Implement

PROCESS MEMORY

Dev Flow remembers the process.

Dev Flow Local-first

Scope
Stage
Verification
Evidence
Recovery

Dev Flow doesn’t replace the agent.
It gives the task a durable process.

Not a sandbox.
Not a coding agent.
Not a cloud platform.

06 Real evidence

Tested with real agent sessions.

Not simulated transcripts.

CodexTwo sessions resumed one Task✓DeepSeekRestart recovery reached DONE✓Stable releasesLifecycle evidence on macOS arm64✓

Currently verified on macOS arm64. View compatibility

Your agent already knows how to code.
Give it a process it can remember.

Install the local lifecycle CLI, then connect the Codex or DeepSeek adapter.