Skip to content

docs(agents): configless tools, and no runtime failures for unsupported code #597

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

Merged
kixelated merged 2 commits into from
Nov 4, 2026
Merged

docs(agents): configless tools, and no runtime failures for unsupported code #597

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd1327f
docs(agents): make every tool configless, with renames inline
kixelated Nov 4, 2026
3212bca
docs(agents): refuse unsupported constructs at compile, never at run …
kixelated Nov 4, 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
5 changes: 3 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Each project lives in its own top-level directory; the [quest tree](quest/README

- Pull the latest origin changes before working.
- Dig into the root cause and fix it at the source. Never work around a fixable bug with a retry, sleep, or timeout, nor pass a flaky test by loosening its assertion.
- Fail loud and early. An unsupported construct or malformed input is an error with a source span, never a warning or a silent fallback.
- Fail loud and early. An unsupported construct or malformed input is a compile error with a source span, never a warning, a silent fallback, or a runtime failure. Generated code panics only where the Rust source does.
- Generated output must match the source's semantics exactly: integer widths and overflow, drop order, laziness, and error paths. Prove it with differential tests against native Rust, not by inspection.
- Reproduce bugs before fixing them. Tests must be worth their weight long-term: cover edge cases, not old bugs or trivial values.
- Keep the PR to one problem: no unrelated refactors, formatting churn, or drive-by changes. Fix every instance of that problem in the same PR.
Expand All @@ -31,7 +31,8 @@ Each project lives in its own top-level directory; the [quest tree](quest/README

- Prefer upstream and maintained crates over hand-rolling. Measure before claiming an improvement over them.
- Every change needs a consumer that uses it now and is worth its cost; name it in the PR. moq is the first consumer of every project here.
- Translators take stock crates as they are: no annotations, and no config beyond true platform boundaries. Each config key or source change a consumer needs is a gap to close.
- Everything is configless, with opinionated names and defaults. Translators take stock crates as they are: no annotations, and no config beyond true platform boundaries. Each config key or source change a consumer needs is a gap to close.
- A vanity rename, if ever supported, is opt-in and lives inline in source next to the item, never in a config file.
- Deleting code is better than adding code.
- Comments explain the non-obvious why, never the history.
- New dependencies use the newest stable version. Do not bump package versions unless asked.
Expand Down