Skip to content

get-shit-done output hook causes crash #22186

Description

@businesscasual98

What happened?

Repeatedly, when a get-shit-done output is almost finished (printing user summary), it crashes gemini with the following message: Once the containers are up, wait about 30 seconds for the database to initialize, then verify:

  • Main App: Open https://localhost:4001 (https://localhost:4001) in your browser. (You will see a certificate warning; click "Advanced" and "Proceed to localhost").
  • Check Login: Try to log in. If the page loads and you can log in, the database migrations and seed data worked.

⠋ Define and manage connections to MCP servers (settings.json)… (esc to cancel, 14s)
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
YOLO ctrl+y
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

  • AbortError: The user aborted a request.
    at abort (/home/businesscasual98/.nvm/versions/node/v22.18.0/lib/node_modules/@google/gemini-cli/node_modules/node-fetch/lib/index.js:1458:16)▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
    at AbortSignal.abortAndFinalize (/home/businesscasual98/.nvm/versions/node/v22.18.0/lib/node_modules/@google/gemini-cli/node_modules/node-fetch/lib/index.js:1473:4) /model Auto (Gemini 3)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:827:20)
    at AbortSignal.dispatchEvent (node:internal/event_target:762:26)
    at runAbort (node:internal/abort_controller:486:10)
    at abortSignal (node:internal/abort_controller:463:5)
    at AbortController.abort (node:internal/abort_controller:505:5)
    at GeminiClient.processTurn (file:///home/businesscasual98/.nvm/versions/node/v22.18.0/lib/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/core/client.js:481:28)
    at processTurn.next ()
    at GeminiClient.sendMessageStream (file:///home/businesscasual98/.nvm/versions/node/v22.18.0/lib/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/core/client.js:579:32)

What did you expect to happen?

Finish output without crashing

Client information

Client Information

Run gemini to enter the interactive CLI, then run the /about command.

│ About Gemini CLI │
│ │
│ CLI Version 0.33.0 │
│ Git Commit 6ee19e1 │
│ Model Auto (Gemini 3) │
│ Sandbox no sandbox │
│ OS linux │
│ Auth Method Logged in with Google ([email protected]) │
│ Tier Gemini Code Assist for individuals │
│ IDE Client VS Code

Login information

Google Account

Anything else we need to know?

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Qualityeffort/medium2-3 days: UI state, async flow, cross-component refactorskind/bugpriority/p1Important and should be addressed in the near term.status/need-informationworkstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions