dongarandClaude Opus 5.5 3b6aae92c5
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m20s
Keep Gitea threads watched across restarts and interruptions
- Record a comment cursor per thread (board.last_comment, the field that
  already existed unused; pr.last_comment), advanced durably when a
  comment is taken up. CommentPoller.resume_after() skips comments at or
  below it, so re-attaching needs no request and cannot replay.
- Boot re-attaches the plan watch at an open gate and the review watch in
  PR_OPEN from their cursors, catching up on comments posted while the
  agent was down (#59). Data saved without a cursor skips what is there,
  so an old approval cannot approve the current revision.
- A restart in PR_OPEN resumes with a notice instead of the restart
  question (#58). A stored restart question for PR_OPEN returns to it on
  either reply instead of re-planning the milestone.
- A stopped or failed review response gets its own pending kind; the
  reply returns to PR_OPEN and resumes the watch from the cursor, so
  comments that arrived meanwhile are delivered. It used to return to
  milestone sign-off, where starting the milestone would open a second PR.
- Comments ignored because of the state leave the cursor alone, so they
  are delivered once the agent is back where they apply.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
2026-09-29 17:33:41 +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 A)
nisse-dev/ Dev Agent — plans and implements software projects (Part B)
nisse-ops/ Sysadmin Agent — operates infrastructure (Part C)

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-Build-Spec.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%