Skip to content

Make agent chat replies a status line, not a document #546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MelbourneDeveloper wants to merge 3 commits into
base: main
Choose a base branch
from
+1 −0
Open

Make agent chat replies a status line, not a document #546

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
170cd6e
Link the integration suite once instead of 176 times
claude Aug 22, 2026
e37cc75
Merge main: the suite consolidation landed ahead of this branch
claude Sep 14, 2026
e89d33c
Make chat replies a status line, not a document
claude Sep 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ REPLACE BROKEN CODE; DON'T WRITE NEW CODE WITH A DUPLICATE PATH

- ⚠️ **Never kill a VS Code process**, including browser-hosted instances. The user cannot recover from this.
- ⚠️ **Never host a report anywhere.** No Claude artifacts, no hosted pages, no external upload — for any result, scorecard, comparison or audit. **Every report is a markdown file, in this repository, produced MECHANICALLY by the code that ran the measurement.** A report typed up by an agent is not a report: the numbers cannot be reproduced, cannot be diffed, cannot be re-run, and the agent is free to be wrong. If a figure is worth reporting, the tool that measured it emits it. Point the user at the file path.
- ⚠️ **Headlines only. No essays.** Chat replies are a status line, not a document: the result, the number that moved, the file path. No restating the request, no narrating the steps taken, no tables the emitted report already contains. Use an emoji to mark anything critical — 🛑 a blocker, 🔴 a regression or failing gate, ✅ a pass — so it is findable at a glance. Detail belongs in the mechanically-produced report above; point at it instead of retyping it.
- ⚠️ **No git.** No `add`, `commit`, `push`, `checkout`, `merge`, `rebase`, `worktree`. Never push to `main`, never stamp yourself as co-author. One branch at a time; never start a new branch when a feature branch exists; converge branches before other work. CI handles git. (`gh issue create` excepted.)
- ⚠️ **No using text pattern matching on source code or structured data. No RegEx on code**. USE THE AST!
- ⚠️ **Token discipline.** Check file size before reading. `Grep` over `Read`; use `offset`/`limit`. Smallest diff that solves the problem. Delete dead code, unused imports, stale comments. Call out irrelevant context — bloat degrades reasoning.
Expand Down