dongarandClaude Opus 5.5
d44581539b
nisse-ui (X6) shows the operator each agent's work and, per item, a walkthrough down to every model request and response, for studying how context, compaction and memory work. It reads each agent's state store, call record and memory folder through read-only mounts, so agent code is unchanged and each agent stays the only writer of its state; it is released with the agents and tested against stores their own code wrote. The call record (L7) is new in nisse-core: every request as sent, the raw response with its reasoning, timing, tokens, prompt reuse and each message's provenance. It is diagnostic only, never read by the agent, and deleted at start, so it never migrates. Commands from the page, including a hold on a task or a whole agent, are an open question (Part Q). The shared database first proposed in #109 is dropped. The plan gets M6.6. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
Nisse
Two self-hosted AI agents sharing a common library, named for the Nordic farm spirit that keeps the place running overnight and expects to be treated well in return.
| Package | Role |
|---|---|
nisse-core/ |
Shared library both agents sit on (Part L) |
nisse-dev/ |
Dev Agent — plans and implements software projects (Part D) |
nisse-ops/ |
Sysadmin Agent — operates infrastructure (Part O) |
One repository, three packages. The library does not exist as code yet: it is
extracted from nisse-dev once that agent works (build-order step 10), as a
package split within this tree.
Architecture
The system-level specification lives at
docs/Architecture.md. It covers the
shared library, both agents, the supporting services, the build order, and the
remaining open decisions.