Scope creep
A precise fix can quietly turn into permission to improve everything nearby unless the original boundary stays visible.
- Fix this API
- Refactor nearby code
- Unrelated work
Codex · DeepSeek · Claude Code · ZCode
Long-running AI coding,
under control.
Your coding agent decides what to do next.TaskBelay keeps the task under control.
01The problem
A good next step
still needs a boundary.
An agent can choose a useful next action. The task still needs an agreed scope, a verification limit, and a state to continue from.
Verification spiral
A targeted check can grow into an open-ended search for more confidence unless the verification limit stays attached to the Task.
- Targeted test
- Full suite
- Platform matrix
The chat ends. The task state should not.
SESSION 1IMPLEMENT → TEST
interrupted
SESSION 2“Let me inspect the repository…”
02How it works
Agree on the task. Work within its bounds.
- 01
Assess, then agree on the plan
Choose direct development for a small change, or TaskBelay for a durable Task. Approve the requirements, design, files, and checks before implementation.
- 02
Keep changes and checks within the plan
Compare actual changes with approved files. Record why more verification is needed before increasing its budget.
- 03
Resume the next valid action
The next session reads the same Task and continues the remaining work instead of reconstructing progress.
Your plan, before the first edit.
Review requirements, design, work items, files, and verification together. Implementation begins after approval. A revised plan or wider file scope needs a new decision.
Choose where the work belongs.
Keep your existing setup, or explicitly choose a separate worktree.
One active Task per directory. Resume in the original workspace. Finishing a Task keeps your directory and branch.
03Capabilities
Four capabilities.
One task under control.
Explicit Scope
Keep the task boundary explicit.
The approved files stay attached to the Task. Actual changes are checked against the plan; supported structured writes can ask before going out of scope.
An extra file needs a decision: allow once, revise the plan, or restore it.
- Allowed
- ✓ packages/auth/**
- Acceptance
- ✓ lock after 5 failed attempts
- Out of scope
- × database/** · unrelated refactors
Bounded Verification
Test enough.Not forever.
Plan checks around the change. Record a concrete gap before adding budget; repeated identical failures pause the loop for a decision.
Example · planned verification2 of 4 commands
✓ Within the current plan
A justified increase is recorded. Extra budget does not mean a test passed.Durable State
Resume the task.Not the chat.
The local Core holds the authoritative Task state. Resume in the original directory; changes invalidate checks that depend on older content.
TaskBelayTask recoveryTASKFix the login retry bug.
- STATE
- TEST
- Revision
- 5
- REMAINING
- 1 targeted check
SAME TASKFix the login retry bug.
- STATE
- TEST
- Revision
- 5
- NEXT
- Run the remaining targeted check
- ✓Scope retained
- ✓Stage retained
- ✓Remaining work retained
SESSION 1: Fix the login retry bug., STATE TEST, Revision 5, 1 targeted check. HOST RESTART. SESSION 2: SAME TASK, STATE TEST, Revision 5, Run the remaining targeted check.
Safe Recovery
Read the saved Taskbefore retrying.
When a TaskBelay submission result is uncertain, read the saved operation before retrying. Blocked tasks retain the reason and recovery information.
- Action↓
- result uncertain↓
- read Task + Recovery↓
- continue · block · retry
04Control Center
See the task state
outside the chat.
Read the same saved Task your agent uses: workspaces, file scope, checks, blockers, and recovery. Explore the example below.
Representative local view
CODEX · LOCAL TASK
Fix the login retry bug.
task-auth-exampleTestTEST
Implementation is complete. Run the planned checks against the current repository content.
- Acceptance
- Lock after 5 failed login attempts.
Retained timeline
- 01Plan approved
- 02Implementation completed
- 03Targeted verification
Create Tasks in Codex, DeepSeek, Claude Code, or ZCode. The local WebUI shows saved Tasks and lets you handle scope, verification, and recovery decisions.
New branch · same directory
- Task branch
codex/login-retry
Manual edits and external tools are observed too. A new file needs a recorded scope decision.
Approved file scope
src/auth/retry.tstests/auth/retry.test.ts
- Outside the plan
- Database changes and unrelated refactors
2 / 4automatic commands used
Need to rerun a check or cover a new risk? Record the reason and required increase before continuing.
Verification
- Retry limit test✓ Passed
- Type check✓ Passed
Checks must match current content. Changing a dependency invalidates affected results.
A response was lost
The client is uncertain whether its submission succeeded. Read the saved operation before deciding to recover or retry.
- Read the saved operation
- Check whether it was committed
- Continue from the saved Task
When work needs attention
File scope, repeated verification, and history conflicts retain a reason and the decision needed to resume.
Create Tasks in Codex, DeepSeek, Claude Code, or ZCode. The local WebUI shows saved Tasks and lets you handle scope, verification, and recovery decisions.
These views illustrate product capabilities; they do not connect to your local Task data.
05Desktop pet
Keep your tasks
within sight.
Meet Dudu, the blue sea sprite keeping you company through long tasks. See saved Task states and open the corresponding Control Center.
Needs a scope decisionLogin retry limit
Running planned checksSearch response cache
Several tasks, one glance
Stacked bubbles show multiple Tasks. Blocked work takes priority; completed work gives way to unfinished Tasks.
Keep one task in focus
Pin the Task you want to follow. Open its WebUI to inspect the saved work and next step.
Make it yours
Import an appearance, control animations, resize the pet, and start or stop it independently.
Made for macOS and Windows desktops.
Meet the desktop pet ↗06Real evidence
Tested with real agent sessions.
See how real coding sessions picked up saved work and carried it through to completion.
Two sessions resumed the same Task
- The same task resumed
- Progress kept across sessions
- Remaining work ready to continue
Recovered after restart and finished the task
- Saved progress recovered
- The same task resumed
- Work carried through to completion
07Where it fits
Use TaskBelay for work that may outlive the session.
Good fit
- Long-running repository tasks
- Work that may span sessions or days
- Changes with explicit scope and targeted verification
- Tasks that may require rework or recovery
Not needed
- One-off questions
- Code explanations
- Status lookups
- Tiny reversible edits that need no durable progress
TaskBelay manages task scope, verification and saved state. It is not a security sandbox or an OS permission system, and does not intercept every file operation or shell command.
08Install
Install TaskBelay
on your machine.
Run dev-flow to manage your integrations in one place. Start a task in the coding tool you already use.
npm install -g @imotong/dev-flow@latestdev-flow