You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: README iteration - dark diagram, reorganize sections, trim footer
1. Diagram back to dark theme
2. Components section moved to collapsible at bottom
3. Knowledge Categories moved up (between What You Get and How It Works)
4. Preset Bundles moved to collapsible
5. Development section removed
6. Related trimmed to axme only
7. Security/License links removed from footer (broken)
### 1. MCP Server (persistent, runs while VS Code is open)
71
-
72
-
Provides tools for the agent to read and write the knowledge base. All writes go through MCP server code (atomicWrite, correct append) - the agent never writes storage files directly. This guarantees format consistency.
73
-
74
-
### 2. Hooks (fire on every tool call)
64
+
## Knowledge Categories
75
65
76
-
**pre-tool-use**: Checks every Bash command, git operation, and file access against safety rules. Blocks violations before they execute. Also creates/recovers session tracking.
|**Handoff**| Where work stopped, blockers, next steps | "PR#17 open, needs review" |
128
-
|**Worklog**| Session history, audit results, events | Timeline of all sessions |
116
+
## Related
117
+
118
+
| Repository | Description |
119
+
|-----------|-------------|
120
+
|[axme](https://github.com/AxmeAI/axme)| AXME platform - durable execution for AI agents |
129
121
130
122
---
131
123
132
-
## Preset Bundles
124
+
<details>
125
+
<summary><strong>Components</strong></summary>
133
126
134
-
During `axme-code setup`, preset bundles provide curated best-practice rules:
127
+
AXME Code has three components:
135
128
136
-
| Preset | What it adds |
137
-
|--------|-------------|
138
-
|**essential-safety**| Protected branches, no secrets in git, no force push, fail loudly |
139
-
|**ai-agent-guardrails**| Verification requirements, no autonomous deploys, proof before done |
129
+
### 1. MCP Server (persistent, runs while VS Code is open)
140
130
141
-
---
131
+
Provides tools for the agent to read and write the knowledge base. All writes go through MCP server code (atomicWrite, correct append) - the agent never writes storage files directly. This guarantees format consistency.
142
132
143
-
##Development
133
+
### 2. Hooks (fire on every tool call)
144
134
145
-
```bash
146
-
npm install
147
-
npm run build # esbuild -> dist/server.js + dist/cli.mjs
148
-
npm test# Node.js test runner (requires Node 22+)
149
-
npx tsc --noEmit # TypeScript strict type check
150
-
```
135
+
**pre-tool-use**: Checks every Bash command, git operation, and file access against safety rules. Blocks violations before they execute. Also creates/recovers session tracking.
151
136
152
-
---
137
+
**post-tool-use**: Records which files the agent changed (for audit trail).
138
+
139
+
### 3. Background Auditor (runs after session close)
140
+
141
+
A detached process that reads the session transcript and catches anything the agent forgot to save. Two modes:
142
+
-**Full extraction** - when the agent crashed or the user closed the window without formal close
143
+
-**Verify-only** - when the agent completed the close checklist (lighter, cheaper)
0 commit comments