[Phase 5] cmd_continue return proper exit codes #240

New Issue

shoko · 2026-04-08T06:30:41+02:00

shoko commented

2026-04-08 06:30:41 +02:00

Problem

uses for all errors, making it difficult for the daemon to distinguish between recoverable errors (max agents) and actual failures.

Solution

Modify and to return proper exit codes:

Exit Code	Meaning
0	Success - agent forked successfully
1	General error - worktree/session/validation failed
2	Max concurrent agents reached (MAX_CONCURRENT_AGENTS limit)

Key changes:

should NOT - return exit code instead
should NOT - return the exit code from
Return exit code 2 when max agents is reached (don't exit, return)

Also create documenting all exit codes.

Status

READY - No dependencies

Files

(new file)

Parent: #235

## Problem uses for all errors, making it difficult for the daemon to distinguish between recoverable errors (max agents) and actual failures. ## Solution Modify and to return proper exit codes: | Exit Code | Meaning | |-----------|---------| | 0 | Success - agent forked successfully | | 1 | General error - worktree/session/validation failed | | 2 | Max concurrent agents reached (MAX_CONCURRENT_AGENTS limit) | Key changes: 1. should NOT - return exit code instead 2. should NOT - return the exit code from 3. Return exit code 2 when max agents is reached (don't exit, return) Also create documenting all exit codes. ## Status **READY** - No dependencies ## Files - - (new file) ## Related Issue Parent: #235

shoko referenced this issue

2026-04-08 06:30:47 +02:00

[Phase 6] Add dry-run support to cmd_continue #241

shoko referenced this issue

2026-04-08 06:30:50 +02:00

[Phase 7] Daemon isolation - call kugetsu as subprocess #242

shoko closed this issue

2026-04-08 06:33:48 +02:00

shoko referenced this issue

2026-04-08 06:34:39 +02:00

[Phase 6] Add dry-run support to cmd_continue #249

shoko referenced this issue