Improve error messaging when agent exits unexpectedly
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- backend
Research direction
No files, tests, or entry points are named. Start by tracing where the agent process exit is handled and how its status reaches the user; done means normal and error exits clearly state that the session finished and include the available reason.
Written by the indexing model from the issue text.
Description
Description
When the underlying agent exits unexpectedly (e.g., due to no API credits remaining), Gigacode should provide a clear error message indicating that the session has finished and why. Currently, the exit reason is not communicated well to the user.
Examples
- Agent exits due to no credits: should display something like "Session finished: agent exited due to insufficient API credits"
- Agent crashes or exits with an error code: should display the reason and explicitly state the session is over
Expected Behavior
When the agent process exits, Gigacode should:
- Clearly state that the session has finished
- Include the reason for the exit when available
- Distinguish between normal completion and error exits
Actual Behavior
The agent exits without a clear message, leaving the user unsure about what happened.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rivet-dev/sandbox-agent
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rivet-dev/sandbox-agent#313 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rivet-dev/sandbox-agent#146 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
rivet-dev/sandbox-agent#145 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
rivet-dev/sandbox-agent#144 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
rivet-dev/sandbox-agent#143 ·
All issues in rivet-dev/sandbox-agent
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·