docket-agent 0.2.0 → 0.2.1

package/README.md

@@ -7,7 +7,10 @@
 Before your agent acts, it checks a one-page rule file you wrote: allow, ask,
 or deny. After, it leaves a tamper-evident record. Anything you didn't write
 down, the agent must ask about. Plain Markdown in your repo; works with
-Claude, Codex, Cursor, and any MCP client.
+Claude, ChatGPT/Codex, Gemini, Cursor, OpenClaw, Hermes, and any MCP client.
+
+**Install:** `npm install -g docket-agent` · **Docs:**
+[shahcolate.github.io/docket/docs.html](https://shahcolate.github.io/docket/docs.html)
 
 Zero dependencies · plain Markdown + JSONL · MIT
 
@@ -202,6 +205,47 @@ The agent gets four tools:
 Warrant checks made by the agent land in the record too. *"Did the agent
 even ask?"* becomes a grep.
 
+## OpenClaw and Hermes
+
+**[OpenClaw](https://docs.openclaw.ai)** injects your workspace's `AGENTS.md`
+into the agent's system prompt at the start of every session — so compile
+straight into the workspace (fitting, given the story that opens this README):
+
+```console
+$ cd ~/.openclaw/workspace
+$ npx docket-agent init
+$ npx docket-agent new followup --template client-follow-up
+$ npx docket-agent compile --target agents --write
+```
+
+Docket only manages its own marked block inside `AGENTS.md` — your existing
+rules, `SOUL.md`, and the rest of the workspace stay untouched. OpenClaw can
+also run the MCP server for native checks and record entries: add `docket`
+as an MCP server in your OpenClaw config with
+`command: npx, args: ["-y", "docket-agent", "mcp", "--dir", "~/.openclaw/workspace"]`.
+
+**[Hermes](https://hermes-agent.nousresearch.com/docs/)** (Nous Research)
+reads `AGENTS.md` context files too — run the same three commands in the
+directory Hermes works from. For native tools, add docket under the MCP
+servers section of `~/.hermes/config.yaml`:
+
+```yaml
+docket:
+  command: npx
+  args: ["-y", "docket-agent", "mcp", "--dir", "/path/to/your/project"]
+```
+
+Any other agent that reads `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, or speaks
+MCP gets the same treatment — one loop file, every agent under the same
+warrant.
+
+## Documentation
+
+The full guide — concepts, loop-file reference, the verdict algorithm,
+matching semantics, record internals, CLI reference, and per-tool setup —
+lives at **[the docs site](https://shahcolate.github.io/docket/docs.html)**.
+The normative format definition is the [Loop File Spec](spec/SPEC.md).
+
 ## Five questions, then the loop exists
 
 `docket new <name>` interviews you:
@@ -275,7 +319,7 @@ Read the [Loop File Spec](spec/SPEC.md) — it's short on purpose.
 - [ ] `docket check` as a Claude Code PreToolUse hook recipe
 - [ ] Loop inheritance (`extends:`) for team baselines
 - [ ] Record export → human-readable work summaries
-- [ ] Adapters: OpenAI custom instructions, Gemini, Windsurf
+- [ ] Adapters: OpenAI custom instructions, Windsurf
 
 ## Contributing
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docket-agent",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "The permission layer and paper trail for AI agents. Your agent checks a rule file before it acts - allow, ask, or deny - and leaves a tamper-evident record after.",
   "type": "module",
   "bin": {

package/src/cli.js

@@ -37,7 +37,7 @@ ${bold('The record')}
   ${cyan('record verify')}             verify the hash chain end to end
 
 ${bold('Portability')}
-  ${cyan('compile')} [--target claude|agents|cursor|raw] [--loop <name>] [--write]
+  ${cyan('compile')} [--target claude|agents|gemini|cursor|raw] [--loop <name>] [--write]
                              render loops into CLAUDE.md / AGENTS.md / Cursor rules
   ${cyan('mcp')}                        run the MCP server (stdio) for agent integration