dongarandClaude Opus 5.5 33d030590d
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m58s
CI / e2e (pull_request) Successful in 7m41s
nisse-review marks a reply that settles its thread; the PR's author resolves it
The reviewer is read-only (R3), so Gitea refuses it resolving a thread.
Now each reply says whether it settles its thread, and a settled reply
carries <!-- nisse-review: settled -->. nisse-dev, as the author, resolves
every comment on that thread's line when it watches the PR, and doesn't
take the settled reply as a point to answer. scripts/resolve_settled.py
does the same for PRs made by hand.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
2026-10-19 22:06:56 +00:00
2026-09-29 18:52:06 +00:00
2026-10-13 22:34:02 +00:00
2026-10-08 23:05:45 +00:00
2026-10-13 22:34:02 +00:00

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.

S
Description
LLM Agents for specialized tasks.
Readme
4.4 MiB
1 Stars 2 Watchers 0 Forks
v0.1.0
Latest
2026-10-07 22:39:30 +00:00
Languages
Python 98.1%
Shell 1.6%
Dockerfile 0.3%