shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

[Phase 5] cmd_continue return proper exit codes #248

New Issue
Closed
opened 2026-04-08 06:34:37 +02:00 by shoko · 0 comments
shoko commented 2026-04-08 06:34:37 +02:00
Owner
Copy Link

Problem

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

Solution

Modify cmd_continue and fork_agent 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. fork_agent() should NOT exit - return exit code instead
  2. cmd_continue() should NOT exit 1 - return the exit code from fork_agent()
  3. Return exit code 2 when max agents is reached (do not exit, return)

Also create EXITCODES.md documenting all exit codes.

Status

READY - No dependencies

Files

  • skills/kugetsu/scripts/kugetsu-session.sh
  • EXITCODES.md (new file)

Related Issue

Parent: #235

## Problem cmd_continue uses exit 1 for all errors, making it difficult for the daemon to distinguish between recoverable errors (max agents) and actual failures. ## Solution Modify cmd_continue and fork_agent 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. fork_agent() should NOT exit - return exit code instead 2. cmd_continue() should NOT exit 1 - return the exit code from fork_agent() 3. Return exit code 2 when max agents is reached (do not exit, return) Also create EXITCODES.md documenting all exit codes. ## Status **READY** - No dependencies ## Files - skills/kugetsu/scripts/kugetsu-session.sh - EXITCODES.md (new file) ## Related Issue Parent: #235
shoko added the ready label 2026-04-08 06:38:28 +02:00
shoko closed this issue 2026-04-08 08:42:32 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label ready
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#248
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?