From 47c175c550c76ab3286c8edb3e32a0ee1583a1c7 Mon Sep 17 00:00:00 2001 From: fredericrous Date: Wed, 7 Oct 2026 14:20:32 +0200 Subject: [PATCH] docs(claude): relais routing is policy only relais is now a Claude Code plugin (v0.10.0): runs start through its tool, and its /relais skill carries how to start, follow and read a run. What stays here is the one thing the plugin cannot know: to route bounded tasks through relais without being asked. The CLI mechanics (cd to the repo root, the dirty-tree rule, reading the outcome) are dropped. Co-Authored-By: Claude Opus 5.5 --- dot_claude/CLAUDE.md.tmpl | 23 ++++++----------------- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git a/dot_claude/CLAUDE.md.tmpl b/dot_claude/CLAUDE.md.tmpl index 7d7bc1c..0ae6feb 100644 --- a/dot_claude/CLAUDE.md.tmpl +++ b/dot_claude/CLAUDE.md.tmpl @@ -295,24 +295,13 @@ only the person may overrule a `rework`. ## Relais routing -In a repo that has `relais.toml` and a trust grant (`relais doctor` is -green there), route bounded implementation and inspection tasks through -the `relais` skill without being asked: one objective, a write scope, and +In a repo with `relais.toml` and a trust grant, route bounded +implementation and inspection tasks through relais (the plugin's +`/relais` skill) without being asked: one objective, a write scope, and acceptance a command can verify. Keep design, multi-repo, ops and -exploratory work in the parent session. Say in one line which path a task -took and why; a repo without a policy gets ordinary work, stated as such. - -- Every relais command runs with the repo (or task worktree) root as cwd - (`cd && relais …`); the session's own cwd is usually - `~/Developer/Perso`, which is not a repo. The CLI finds `relais.toml` - upward from any subdirectory, never from outside the repo. -- `relais run` refuses a dirty tree and builds its candidate in its own - worktree from the base SHA, so commit (or finish) unrelated work first; - the worktree-isolation rule above still governs anything the parent - edits by hand. -- A run's outcome, not a worker's completion message, is the acceptance. - `needs_decision` is the user's call unless the answer is already in the - request. +exploratory work in the session, and say in one line which path a task +took. `needs_decision` is the person's call unless the request already +answers it. ## Security