Run Gortex post-task diagnostics when the agent finishes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- ai-infra-agents, developer-experience
Research direction
Start with internal/hooks/pi.go around bridgeEventSlot and internal/hooks/posttask.go lines 71–113, then trace recordSessionWriteTargets in session_paths.go and the extension's Pi event forwarding. First determine which Pi event and delivery mode can resume the agent after it stops. Done means session-scoped diagnostics and localization checks run at task end, blocking continues the agent, and non-blocking results are shown; the issue leaves rendering and timeout behavior open.
Written by the indexing model from the issue text.
Description
Feature
Run Gortex's post-task diagnostics when the Pi agent finishes, matching Claude Code's Stop hook.
On Stop, Claude gets "Gortex Post-Task Diagnostics" built from detect_changes -> explain_change_impact, get_test_targets, check_guards, analyze and contracts, scoped to the files this session wrote. The same hook checks localization claims in the last assistant message and can return decision: block so the model keeps working (internal/hooks/posttask.go L71-113).
What exists
- The Pi bridge has no stop slot (
bridgeEventSlot,internal/hooks/pi.goL150-161). - Session write targets are recorded only on the Claude path (
recordSessionWriteTargets,session_paths.goL161).
Sketch
- Gortex: record write targets in the Pi tool_call slot; add a
stop/agent_endslot returning diagnostics and a block flag. - Extension: forward Pi's
agent_endwith the last assistant text; on block, queue a follow-up message so the agent continues; otherwise show the diagnostics.
To investigate
- Which Pi event and delivery mode can continue the agent after it stopped.
- How diagnostics should render (displayed to the user, sent to the model, or both).
- Cost on large diffs; a timeout bigger than the 5 s hook budget may be needed.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 10h 45m
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 gortexhq/pi
-
dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
b:minor bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
software-mansion/argent#1698 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
redhat-developer/rhdh-plugin-export-overlays#4624 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
better-auth/better-auth#12132 · 1 reaction ·
Maintainers usually reply within 1 day
-
automation missing-model model-sync provider:tinfoil
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/models.dev#12053 ·
Maintainers usually reply within 1 day
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hurttlocker/o8#5112 ·