Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

docs(agents): let other tools own their conventions (#4435)

Maximilian Roos40cee1efea8b
diff --git a/AGENTS.md b/AGENTS.md
index 4d0dceb9a..89997e765 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -94,10 +94,14 @@ codecov/patch is a merge gate even if GitHub marks it optional. Fix real gaps; d
### Use Existing Dependencies
-Check Cargo.toml and installed APIs before writing a utility. Prefer path_slash for path normalization, shell_escape for shell quoting, color_print for ANSI styling, and MiniJinja's undeclared_variables for template variables. Let dependencies own their own rules.
+Check Cargo.toml and installed APIs before writing a utility. Prefer path_slash for path normalization, shell_escape for shell quoting, color_print for ANSI styling, and MiniJinja's undeclared_variables for template variables.
Name pure accessors as bare nouns, erroring preconditions require_*, network calls fetch_*, and file loads load_*; avoid get_*.
+### Other Tools Own Their Conventions
+
+Where another tool owns a convention, such as its config location, file format, URL syntax, or error reporting, ask that tool or a library that implements its rules instead of encoding them in Worktrunk: `nu` reports its own directories, and `gh auth token --hostname` reports whether a host is authenticated. Worktrunk's role is the standard uses of those conventions. Where neither the tool nor a library answers, support the standard case and remove rather than refine: an input that only misbehaves outside standard use is a reason to stop reading it, and a tool that isn't installed has nothing to integrate with, so needs no fallback table.
+
### System Docstrings
Complex state machines and cross-module coordination need a module-level spec describing purpose, decisions, and invariants. Keep it current as the system changes.