zchee / zchee/ganja-code

Self-authored tripwires: a watch tool

Open
#61 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

idea size:L verdict:do
Dominant language
Rust
Stars
2
Forks
0
Avg merge
1h
Merged PRs (30d)
17

Description

What it does

Adds a watch tool with which the model registers a few ways the current task could go off course. The engine checks the results of edits, writes and shell commands against them and appends a note only when one fires. Calling watch raises a dialog that names what will be sent; a list-and-release view lets the user see and clear the tripwires.

Source

Outside beads: one of four proposals for using Jev judgments in ganja, carried into the map by its destination (#33, #34, #35).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

  • Direction (README): The README does not mention Jev. The nearest passage is the isolation bullet's "blast radius of a poisoned prompt or a bad tool call" (README.md:23-27).
  • Today's terminal users: A user running a long task learns when the work drifts from what the model itself said would be a mistake, without reading every step.
  • Evidence: No watch tool exists. Accuracy is unmeasured; measuring it is part of the work.

Depends on

Blocked by the judge seam and the [evaluate] table of #59. The proposal is a new tool in ganja-tool, one seam on ToolCtx, questions kept in the engine so they survive compaction, and a list-and-release UI.

Verdict

  • Verdict: do
  • Size: L — a new tool, an engine seam and a new UI surface; several plans.
  • Exception to the probe rule: yes. #36 says an idea that needs a measurement or a probe first is not do; this one is an explicit exception: measuring accuracy is part of the work.
  • Date: 2026-09-19
  • Verdict ticket: #47

Theme: #50

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the judge seam and the [evaluate] table from #59, then inspect ganja-tool and ToolCtx. The proposal calls for a watch tool, engine checks that preserve questions through compaction, and a list-and-release UI. Done includes measuring accuracy and delivering all of these surfaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.