Dodaios is an open-source agent OS for your desktop: it runs your coding agents, browser and apps by voice or chat, on your own machine. Formerly Personal Jarvis.
Python agent-orchestrationai-agentai-coding-assistantclaude-codecoding-agentcomputer-usedesktop-applocal-firstmcppersonal-jarvisvoice-assistantvoice-coding
docs(agents): trim AGENTS.md to always-needed rules
rubenluetke10-beepb29bc45ece8a
diff --git a/AGENTS.md b/AGENTS.mdindex ad39cb5f0e..c04d6ff5dc 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -1,15 +1,15 @@# Personal Jarvis agent rules-The binding rules for every coding agent in this repo — Claude Code, Codex,-Gemini CLI, whichever. This is the whole rulebook; there is no longer a fuller-version to read first. Write everything here so it addresses ANY agent.+The binding rules for every coding agent in this repo: Claude Code, Codex,+Gemini CLI, whichever. Write everything here so it addresses ANY agent.**Source of truth:** `AGENTS.md` is the only instructions file; every agentreads it directly. Never add a `CLAUDE.md`, `.claude/CLAUDE.md` or`CLAUDE.local.md`: Claude Code then reads that file INSTEAD of this one(`scripts/ci/check_agents_md.py` blocks a tracked one). A Claude pane on aJarvis account config dir sees `~/.claude/CLAUDE.md` as such a parent-dir file,-so its Project instructions setting must be `claude-md-and-agents-md`.+so its user settings need the agents-md built-in plugin's `instructionFiles`+option set to `claude-md-and-agents-md`.Edit `.agents/{agents,skills}/`; `.claude/{agents,skills}/` are compatibilitycopies because Claude Code does not discover subagents or skills under`.agents/`, and `.codex/agents/*.toml` is generated from `.agents/agents/*.md`@@ -61,7 +61,8 @@ These cost real bugs. Nothing catches them but you.fix is `npm run build` in `jarvis/ui/web/frontend/` and nothing else; openwindows reload themselves (`src/lib/bundleWatch.ts`). Never end a frontendchange by asking for a restart.-- **Read `MEMORY.md`** (`~/.claude/projects/.../memory/`) before larger decisions.+- **Check your project memory before larger decisions** where your CLI keeps+ one (Claude Code loads its `MEMORY.md` index automatically).## 2. What the product is@@ -99,10 +100,9 @@ copied from, or made to match it. Preserve required copyright, license andattribution notices and factual dependency, integration and compatibilityreferences; this rule never authorizes concealing code provenance.-**Proportionality.** The agent owns the validation plan and chooses the smallest-set of checks that can detect a plausible regression from the diff. State the-scope, what was run, and what remains unverified in the PR. Use these tiers as-guidance, not as automatic checklists:+**Proportionality.** You own the validation plan: the smallest set of checks+that can detect a plausible regression from the diff. State the scope, what+ran, and what remains unverified in the PR. Tiers are guidance, not checklists:- **T1 local:** for copy, styling, docs, one view, or an isolated refactor, runfocused checks for that surface. A frontend change still needs a production@@ -116,14 +116,12 @@ guidance, not as automatic checklists:behavior changes. A new provider or credential path needs a fresh-install,one-key proof; a schema-only change does not automatically owe that test.-Escalate evidence when risk crosses a boundary, not because a label is-ambiguous. Do not claim unrun platforms, devices, or providers were verified.-If a required check is red on the exact base commit, compare failure identities-and causes under the same environment. A failure already present on base may-be reported as a separate backlog item; a new failure or an unexplained change-in a failing test blocks completion. Counts alone are not a comparison. Do not-silence a required check, raise a baseline, or bypass branch protection to make-a PR appear green.+Escalate evidence when risk crosses a boundary. Never claim an unrun platform,+device or provider was verified. A check red on the exact base commit: compare+failure identities and causes in the same environment (counts are not a+comparison); a failure already on base is a backlog item, a new or changed+failure blocks completion. Never silence a required check, raise a baseline,+or bypass branch protection to look green.## 3. Architecture you must respect@@ -147,20 +145,10 @@ Two the gates catch but models still write: never swallow an exception withoutlogging, re-raising, or saying why silence is right (AP-30), and never add aconfig field nothing reads (AP-31).-Marketplace plugin auth follows the browser-auth standard-(`docs/marketplace/browser-auth-standard.md`): a normal user connects with one-browser approval and zero developer setup; the publisher provisions the shared-OAuth client (`publisher_<family>_oauth_*` secrets), never the end user. A new-auth-bearing plugin is not releasable while its default path needs pasted-tokens, user-supplied client IDs/secrets, or self-registered developer apps —-own-client stays an expert override only. Every catalog change keeps-`docs/marketplace/plugin-auth-audit.md` and `scripts/ci/check_plugin_auth_contract.py`-green; provider error bodies never reach logs, UI, or storage (AP-34).-Keep `docs/marketplace/plugin-e2e-audit.json` backed by real browser evidence;-new built-ins require PASS, and a plugin ships as `acceptance: "verified"` only-with a completed PASS; every other one ships labeled "preview" in the app.-Release qualification runs the auth gate with `--require-e2e-pass`, which also-makes every PASS ship as verified. BLOCKED never means provider-verified or complete.+Marketplace plugin auth: before touching a plugin or the catalog, read+`docs/marketplace/browser-auth-standard.md` (one browser approval, zero+developer setup, publisher-provisioned OAuth client, verified/preview+acceptance from real browser evidence). BLOCKED never means verified.The rest of the register, one line each, because code comments cite thesenumbers: never hardcode an Anthropic/Claude client (AP-6); keep awareness and@@ -172,8 +160,7 @@ it (AP-14); new `[phase6.*]` / `[memory.wiki.*]` keys needwake upgrade only on the out-of-process inference probe, never on CUDA presence(AP-25); verify a wake word on audio energy and candidate shape, never ontranscript content (AP-27); a WebGL scene releases its context and survives-losing it (AP-32); a reconnect without jitter and without a shared connect-budget is an outage of the whole machine, not an app bug (AP-33); a macOS+losing it (AP-32); a reconnect pays the jittered connect budget (AP-33, §1); a macOSfeature asks the OS at first use, from a user gesture, through`jarvis/platform/permission_service.py` — no preflight refuses before the OS wasasked, nothing is asked at launch, nothing acts without a live grant, an agent@@ -182,11 +169,9 @@ Detail and history for any of them: `docs/BUGS.md`.## 4. How work ships-**World and character art:** follow `docs/agent-society/game-art-pipeline.md`-and the `game-art-pipeline` skill before creating/redesigning game assets.-Author a small reference in Blender and verify it in the actual runtime before-rolling its style out across asset families; no separate user approval of the-reference is required. Existing runtime contracts stay binding.+**World and character art:** use the `game-art-pipeline` skill+(`docs/agent-society/game-art-pipeline.md`) before creating or redesigning+game assets.Commit each finished step (Conventional Commits). Use the coding agent'sstandard Git workflow: do not artificially leave completed work local, and do@@ -228,8 +213,8 @@ when changed; nothing a year old or older ships as a default.`run.bat` (`--headless` = API only). Choose focused `pytest` and lint targetsfor the diff; use fakes from `tests/fakes/`, never `unittest.mock`. Run thefull suite when a change has broad reach or focused tests cannot bound its-risk. New providers pass their `tests/contract/` family. Four guards remain-required in CI: `test_routing`, `test_output_filter`,+risk. New providers pass their `tests/contract/` family. Four guards always run+inside `CI gate`: `test_routing`, `test_output_filter`,`test_hangup_reason_parity`, `test_turn_language`.The commit and push hooks block confirmed secret, private-key, withheld-path,