|
1 | 1 | <!-- HARNESS:START |
2 | | - version=0.33.0 |
| 2 | + version=0.34.0 |
3 | 3 | schema=1 |
4 | | - updated=2026-07-19T05:36:09Z |
| 4 | + updated=2026-07-19T12:15:57Z |
5 | 5 | DO NOT EDIT THIS BLOCK — regenerate with: harness-ctl update /Users/patrickbertsch/dev/tqai |
6 | 6 | --> |
7 | 7 |
|
|
24 | 24 | | Max cost / session | $3.00 | |
25 | 25 | | Session token TTL | 15 minutes (re-register to refresh) | |
26 | 26 |
|
| 27 | +## Must escalate (blocks until human approves) |
| 28 | + |
| 29 | +- `create_pr` |
| 30 | + |
| 31 | +- `deploy` |
| 32 | + |
| 33 | +- `spend` |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +## Available tools |
| 38 | +See `harness/TOOLS.md` for full reference with parameter schemas. |
| 39 | + |
| 40 | +- `web_search` — search the web via Brave/Google |
| 41 | +- `web_fetch` — fetch and extract URL content |
| 42 | +- `file_ops` — read/write files within the project root |
| 43 | +- `memory_store` / `memory_search` — per-session key-value memory |
| 44 | + |
| 45 | +## Project overrides (harness.yaml) |
| 46 | + |
| 47 | +*(no harness.yaml found — using manifest defaults)* |
| 48 | + |
| 49 | + |
| 50 | +## How to connect (Claude Code) |
| 51 | + |
| 52 | +The proven way to give a Claude Code session live access to this project's harness |
| 53 | +identity is `harness-ctl mcp-bridge tqai`, registered as a stdio MCP server: |
| 54 | + |
| 55 | +```json |
| 56 | +{ |
| 57 | + "mcpServers": { |
| 58 | + "harness-tqai": { |
| 59 | + "type": "stdio", |
| 60 | + "command": "harness-ctl", |
| 61 | + "args": ["mcp-bridge", "tqai"] |
| 62 | + } |
| 63 | + } |
| 64 | +} |
| 65 | +``` |
| 66 | + |
| 67 | +Add this to `.mcp.json` in this project (or globally in `~/.claude.json`), then reconnect. |
| 68 | +This gives the session this agent's RBAC-scoped tools directly — no manual HTTP calls needed. |
| 69 | +The raw HTTP protocol below is what the bridge does under the hood; use it directly only when |
| 70 | +building a non-Claude-Code integration. |
| 71 | + |
27 | 72 | ## All registered agents (harness fleet) |
28 | 73 |
|
29 | 74 |
|
@@ -58,9 +103,9 @@ Check pending approvals: `harness-ctl pending` |
58 | 103 |
|
59 | 104 | ## Working on this project |
60 | 105 |
|
61 | | -1. **Start from `CLAUDE.md`** at the project root — it is the canonical |
62 | | - entry point for every task/session, listing this agent's active |
63 | | - constraints and where to look next. |
| 106 | +1. **This file is the canonical harness reference for this project.** |
| 107 | + `CLAUDE.md` points here for anything harness-related — project-specific |
| 108 | + rules and conventions live in `CLAUDE.md` itself, below its harness block. |
64 | 109 |
|
65 | 110 | 3. Reference docs, regenerated by `harness-ctl update`: |
66 | 111 | - `harness/TOOLS.md` — full tool schemas and error cases |
|
0 commit comments