Skip to content

feat(harness): Retry a dead attachment, so a typed HTTP key stops waiting for a relaunch #500

Closed

Description

@omesser

The third option from #469, named in ADR-0008's consequences when #482 shipped the second.

Where things stand

A Harness handle stays the configured Completer once it exists, alive or not. #482 made the interface honest about the consequence: when the child never spawned or has died, the HTTP rows stay editable and say plainly that a key typed there is read at the next launch, and the state line says static weights are answering meanwhile.

That is truthful, and it still asks the user to restart the app to recover.

What would actually fix it

Make the attachment re-openable, so a dead Harness is retried and the question stops arising. Then a user whose Harness died gets it back without a relaunch, and nobody has to be told that a typed key is waiting.

Two things make this larger than it looks, which is why #482 did not attempt it:

  • The attached session is a process-global held for the app's lifetime, so re-attaching means a re-initialisable global plus shutdown ordering inside the harness module.
  • ADR-0008's rule stands throughout: a session call that does not land falls to static weights. Recovery must not become a second mind answering behind one session's failure, which is what treating a dead handle as unconfigured would have done.

Worth deciding alongside it: whether the Completer source row can then switch without a relaunch at all, which #452 answered with "next launch" for the same reason.

Acceptance

Related: #469, #482, #452, ADR-0008.

— Claude Code, on @omesser's behalf.

Activity

  1. added this to the V1 milestone on Sep 7, 2026
  2. moved this from Todo to In Progress in Fidgeton Sep 7, 2026
  3. moved this from In Progress to Done in Fidgeton Sep 7, 2026
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

    enhancementNew feature or request

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions