Tell the model once per session when the Gortex daemon is down

Open
  • Is something wrong?
#49 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
ai-infra-agents

Research direction

Read the Pi bridge behavior referenced at internal/hooks/pi.go L224-226 and compare it with the once-per-session notice in internal/hooks/daemon_degraded.go L39. Decide whether the notice belongs in the bridge or the extension’s first-turn warnings, then check how daemon recovery should be handled. Done means the model is informed once per session when the daemon is unreachable, with recovery behavior clarified.

Written by the indexing model from the issue text.

Description

enhancement
Feature

Tell the model once per session when the Gortex daemon is unreachable, matching Claude Code.

Claude gets a single additionalContext notice per session when the daemon is down (internal/hooks/daemon_degraded.go L39). The Pi bridge stands down silently (internal/hooks/pi.go L224-226), so the model keeps calling graph tools that fail.

To investigate
  • Whether the notice belongs in Gortex's Pi bridge (preferred, the text is Gortex's) or in the extension's existing first-turn warnings.
  • Recovery: telling the model when the daemon comes back.
Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
10h 45m
Merged PRs (30d)
20

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gortexhq/pi

All issues in gortexhq/pi

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.