8000 boot-agents.sh reports "launched + armed" while the pane is waiting on a Claude Code prompt · Issue #24 · simon-inkie/inkie-deck · GitHub
[go: up one dir, main page]

Skip to content

boot-agents.sh reports "launched + armed" while the pane is waiting on a Claude Code prompt #24

Closed

Description

@simon-inkie

Problem

A new agent's pane stops at Claude Code's first-run screens: folder trust (unnumbered, default selection is "No, exit"), then the resume picker (see the linked issue on that), then the fullscreen-renderer offer. The script still reports success, so a boot-on-startup produces no working agent and the user is not told. Prompts change between Claude Code versions, so they cannot be enumerated once.

Evidence

Seen in test: multiple runs stalled at the trust screen while the boot script reported "1 launched + armed".

Fix

After launching, sample the pane (reuse the pane-idle / stuck-pane classifiers) and report per agent: ready, or "waiting on a Claude Code prompt: open its terminal in Deck". Recognise the trust screen specifically and say "choose Yes, I trust this folder; do not press Enter, No is preselected". Document this in INSTALL.md tier 3, including that agents run in Claude Code's default permission mode (currently auto) unless configured. Do not write into Claude Code's internal trust config without a decision; it is version-fragile.

Acceptance criteria

  • With a fresh agent, boot-agents.sh exits with a summary naming each agent stuck at a prompt, and a non-zero or distinct exit status for "launched but waiting".
  • INSTALL.md tier 3 has a "first boot" paragraph.
  • Test covers a pane fixture showing the trust screen.

From the 2026-09-27 Windows/WSL install test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0