sam/paperclip-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Project>project overview from the dashboard endpoint; tools chooser drawn in Board>board; docs for Shell and t

Browse Source
This commit is contained in:
Sam
2026-11-10 21:48:03 +11:00
parent 3d31243317
commit 3e90ca82ab
14 changed files with 1225 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

185
.pi/memory-vault/packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns.md
View File

@@ -1304,3 +1304,188 @@ Committed as `7b12b45`. Say go and I run that list end to end and report each re
- context: [[packs/paperclip-harness/20-context/tmp|tmp]]
- runbook: [[packs/paperclip-harness/70-runbooks/tmp-deployment-operations|tmp deployment operations]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|tmp repository structure and configuration patterns]]
---
## Update (2026-11-10 10:01:16)
`GET /api/agents/{id}/skills` returns supported/mode, desiredSkills + desiredSkillEntries (key/versionId), and entries[] with key, runtimeName, versionId, currentVersionId, desired, managed, state, sourcePath, targetPath.
Observed on agent Builder (adapterType pi_local, mode persistent): desired=[`paperclipai/paperclip/paperclip`]; entry `company/d4921013-e5da-4d88-8016-57d5746e2d03/obsidian-cli` has desired=false, managed=true, state=`stale`, runtimeName `obsidian-cli--b74ae42966`, sourcePath under /home/sam/.paperclip/instances/default/skills/<companyId>/obsidian-cli, targetPath under /home/sam/.pi/agent/skills/.
`POST /api/agents/{id}/skills/sync` supports add / remove / replace; `replace` gives an exclusive skill set (keeps sub-agent context small).
Company-level skill management surface: /api/companies/{companyId}/skills (GET,POST, /{skillId} GET/PATCH/DELETE), versions (GET,POST, /{versionId}), files, audit, comments, fork + fork-precheck, rename, reset, star, install-update, update-status, test-inputs, test-runs (+cancel), categories, import, install-catalog, scan-projects, browse-project; skill-policy GET/PUT/DELETE + /evaluate; skill-test-run-templates. Public: /api/skills/{index,available,catalog,catalogId,skillName}; invite-scoped /api/invites/{token}/skills/...
## Evidence
- Confidence: 90%
- Reason: Factual API/state discovery likely to be reused when implementing skills UI or fixing stale skills.
---
## Update (2026-11-10 10:01:16)
`GET /api/companies/{id}/dashboard` returns (observed 1.8 KB): agents {active, running, paused, error} = 6/0/0/0; tasks {open, inProgress, blocked, done} = 8/0/4/147; costs {monthSpendCents, monthBudgetCents, monthUtilizationPercent} = 11/0/0; pendingApprovals 0; budgets {activeIncidents, pendingApprovals, pausedAgents, pausedProjects} all 0; runActivity list of 14. Proposed UI: a Project>overview panel rendering these blocks with a Go sparkline (tuios.dev/plot) instead of embedding the web dashboard.
## Detailed observations from completed turn
Explored all of it. Recorded in `docs/PLAN-INTERFACE.md`; the short version:
## Skills per agent — Paperclip already models it
`GET /api/agents/{id}/skills` returns a desired set, a managed set and a state per skill. On `Builder` today:
```
desired: ["paperclipai/paperclip/paperclip"]
company/<id>/obsidian-cli desired: false managed: true state: "stale"
```
`POST /api/agents/{id}/skills/sync` takes `add`, `remove` or **`replace`** — `replace` is exactly "this agent gets these and nothing else", which is how a sub-agent's context stays small. There is also a company skill catalog, versions, audit, and `GET/PUT /api/companies/{id}/skill-policy` with an `evaluate` call.
Proposal: two rows in `Agents>agents` settings — **skills** (the desired set, read-only first, add/remove later) and **skill source**. A full browser is a later screen, not a panel. Also: `obsidian-cli` sitting `stale` on Builder is worth fixing.
## Memory — three different things
| | state here | what it is |
|---|---|---|
| **engram** | installed, v1.16.1, MCP mode, **not** registered in `~/.pi/agent/mcp.json` (only `codebase-memory`, `graphify-vault`) | persistent memory |
| **headroom** | running, v0.24.0, healthy at `192.168.20.13:8787`, memory backend **disabled**, compression on | a prompt-compression proxy, not a store |
| **pi memctx** | in use now | injects notes into a prompt |
They are complementary. Paperclip's only per-agent lever is `adapterConfig` and `runtimeConfig`, so memory is set per agent by pointing that agent at the proxy or store it should use. Proposal: a **memory** row in `Agents>agents` settings showing which of the three that agent uses, and nothing more until one agent has run both ways and been measured.
## MOUSE-1
`MOUSE_API_KEY` is set (checked the name only, never the value). `JEV_API_KEY` too. No `mouse`, `mouse1`, `jev` or `switch` binary is installed.
There **are** notes, and they are good ones — in the old project's plan documents:
> MOUSE-1 is *"triage only: label, score, route, escalate. Never a gate, never a permit"* — explicitly ruled out for deciding a merge or allowing a tool call, because a cheap classifier that fails open on a network error makes a green run a lie.
I would adopt that policy unchanged. Its place, if added: ordering `Board>board`'s needs-you list, or pre-sorting findings in `Work>review`. Never the merge, never an approval.
## Lazygit
Already wired: `t` in `Board>board` or `Work>work`, choose Lazygit. Verified opening in the right workspace and closing with `q`.
## The old `office` — and what ours lacks
The previous `office` did four things: remember the host; run `new-project` to write the scaffold (`settings.toml`, a file per role, `verify.sh`, the per-screen notes) writing **only what is missing**; refuse if the session does not exist and print the exact `tuios new` line; then build the pages.
Ours does the host, the refusal and the pages — but **no scaffold**. No per-role files, no `verify.sh`, no page notes. That is the cheapest real gap in the whole plan.
## Dashboard — the API answers it in one call
`GET /api/companies/{id}/dashboard`, 1.8 KB:
```
agents {active 6, running 0, paused 0, error 0}
tasks {open 8, inProgress 0, blocked 4, done 147}
costs {monthSpendCents 11, monthBudgetCents 0, utilization 0}
runActivity [14 entries]
```
Proposal: a `Project>overview` panel with those blocks and a sparkline drawn in Go with `tuios.dev/plot`, rather than embedding the web dashboard in a pane.
## Not doing
Artifacts — dropped as instructed.
I am ready for the task you are about to deliver; nothing in the tree is half-changed, the eight workspaces are running, and the last commit is `3d31243`.
## Evidence
- Confidence: 90%
- Reason: Concrete endpoint shape and counts support future Project>overview implementation.; enriched with final-answer detail because persistence should be reusable
---
## Update (2026-11-10 10:01:16)
Three complementary memory mechanisms: (a) engram v1.16.1 installed in MCP mode but NOT registered in ~/.pi/agent/mcp.json; (b) headroom prompt-compression proxy v0.24.0 healthy at 192.168.20.13:8787 with memory backend disabled (memory check enabled=false, backend null) and compression on; (c) pi memctx, which injects notes into a prompt. Registered MCP servers at discovery: only codebase-memory and graphify-vault (both lifecycle lazy). Paperclip exposes only adapterConfig and runtimeConfig per agent, so memory choice is expressed by pointing an agent at the desired proxy/store. Proposal: a memory row in Agents>agents showing which mechanism an agent uses, pending measurement.
## Detailed observations from completed turn
Explored all of it. Recorded in `docs/PLAN-INTERFACE.md`; the short version:
## Skills per agent — Paperclip already models it
`GET /api/agents/{id}/skills` returns a desired set, a managed set and a state per skill. On `Builder` today:
```
desired: ["paperclipai/paperclip/paperclip"]
company/<id>/obsidian-cli desired: false managed: true state: "stale"
```
`POST /api/agents/{id}/skills/sync` takes `add`, `remove` or **`replace`** — `replace` is exactly "this agent gets these and nothing else", which is how a sub-agent's context stays small. There is also a company skill catalog, versions, audit, and `GET/PUT /api/companies/{id}/skill-policy` with an `evaluate` call.
Proposal: two rows in `Agents>agents` settings — **skills** (the desired set, read-only first, add/remove later) and **skill source**. A full browser is a later screen, not a panel. Also: `obsidian-cli` sitting `stale` on Builder is worth fixing.
## Memory — three different things
| | state here | what it is |
|---|---|---|
| **engram** | installed, v1.16.1, MCP mode, **not** registered in `~/.pi/agent/mcp.json` (only `codebase-memory`, `graphify-vault`) | persistent memory |
| **headroom** | running, v0.24.0, healthy at `192.168.20.13:8787`, memory backend **disabled**, compression on | a prompt-compression proxy, not a store |
| **pi memctx** | in use now | injects notes into a prompt |
They are complementary. Paperclip's only per-agent lever is `adapterConfig` and `runtimeConfig`, so memory is set per agent by pointing that agent at the proxy or store it should use. Proposal: a **memory** row in `Agents>agents` settings showing which of the three that agent uses, and nothing more until one agent has run both ways and been measured.
## MOUSE-1
`MOUSE_API_KEY` is set (checked the name only, never the value). `JEV_API_KEY` too. No `mouse`, `mouse1`, `jev` or `switch` binary is installed.
There **are** notes, and they are good ones — in the old project's plan documents:
> MOUSE-1 is *"triage only: label, score, route, escalate. Never a gate, never a permit"* — explicitly ruled out for deciding a merge or allowing a tool call, because a cheap classifier that fails open on a network error makes a green run a lie.
I would adopt that policy unchanged. Its place, if added: ordering `Board>board`'s needs-you list, or pre-sorting findings in `Work>review`. Never the merge, never an approval.
## Lazygit
Already wired: `t` in `Board>board` or `Work>work`, choose Lazygit. Verified opening in the right workspace and closing with `q`.
## The old `office` — and what ours lacks
The previous `office` did four things: remember the host; run `new-project` to write the scaffold (`settings.toml`, a file per role, `verify.sh`, the per-screen notes) writing **only what is missing**; refuse if the session does not exist and print the exact `tuios new` line; then build the pages.
Ours does the host, the refusal and the pages — but **no scaffold**. No per-role files, no `verify.sh`, no page notes. That is the cheapest real gap in the whole plan.
## Dashboard — the API answers it in one call
`GET /api/companies/{id}/dashboard`, 1.8 KB:
```
agents {active 6, running 0, paused 0, error 0}
tasks {open 8, inProgress 0, blocked 4, done 147}
costs {monthSpendCents 11, monthBudgetCents 0, utilization 0}
runActivity [14 entries]
```
Proposal: a `Project>overview` panel with those blocks and a sparkline drawn in Go with `tuios.dev/plot`, rather than embedding the web dashboard in a pane.
## Not doing
Artifacts — dropped as instructed.
I am ready for the task you are about to deliver; nothing in the tree is half-changed, the eight workspaces are running, and the last commit is `3d31243`.
## Evidence
- Confidence: 85%
- Reason: Durable operational facts about memory components and configuration gaps.; enriched with final-answer detail because persistence should be reusable
## Related learned memories <!-- same-turn-2026-11-10 10:01:16 -->
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|Paperclip per-agent skills state and sync semantics]]
- runbook: [[packs/paperclip-harness/70-runbooks/tmp-deployment-operations|Adopt an existing folder into the harness with `office` (and its known scaffold gap)]]
- decision: [[packs/paperclip-harness/50-decisions/mouse-1-restricted-to-triage-never-a-gate-or-permit|MOUSE-1 restricted to triage; never a gate or permit]]
- action: [[packs/paperclip-harness/40-actions/2026-11-10-wrote-docs-ui-layout-md-and-three-live-layout-mockups|Recorded interface plan for Paperclip + TUIOS harness in docs/PLAN-INTERFACE.md]]
- session: [[packs/paperclip-harness/80-sessions/paperclip-tuios-interface-discovery-skills-api-memory-stack-|Paperclip-TUIOS interface discovery: skills API, memory stack, MOUSE-1, dashboard, old office scaffold]]
- context: [[packs/paperclip-harness/20-context/paperclip-tuios-harness-sam-s-coding-harness-office-board-wo|Paperclip-TUIOS harness (sam's coding harness: office/board/work screens)]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-paperclipai-2026-11-10-10-01-16|Rich discovery: paperclipai 2026-11-10 10:01:16]]
- context: [[packs/paperclip-harness/20-context/home|paperclipai]]