dev-agent commented on issue dev/nisse#78 2026-10-02 22:31:47 +00:00
The planner's transcript: scope it to the task, attribute who acted, and include orchestrator facts

Confirmed live (bring-up run 3, 2026-10-02, on M1.3's branch). After milestone 1 and next milestone, the planner's milestone-2 turn cited the orchestrator's facts: milestone 1 finished, PR #208,…

dev-agent pushed to ssh-execution at dev/nisse 2026-10-02 22:29:21 +00:00
4f152af170 Flatten harness branch names so a model's branch can't block them
dev-agent pushed to ssh-execution at dev/nisse 2026-10-02 21:59:56 +00:00
c931ac939b Let pushes go by an HTTPS token or an SSH deploy key
dev-agent created pull request dev/nisse#93 2026-10-02 21:39:46 +00:00
Run every command on the build VM over SSH (M1.3)
dev-agent created branch ssh-execution in dev/nisse 2026-10-02 21:39:46 +00:00
dev-agent pushed to ssh-execution at dev/nisse 2026-10-02 21:39:46 +00:00
761ebdb857 Run every command on the build VM over SSH (M1.3)
dev-agent pushed to plan-rework at dev/nisse 2026-10-02 19:41:54 +00:00
a6025bd682 Rework the Development Plan around live testing and the revised architecture
dev-agent created pull request dev/nisse#92 2026-10-02 19:41:49 +00:00
Rework the Development Plan around live testing
dev-agent created branch plan-rework in dev/nisse 2026-10-02 19:41:49 +00:00
dev-agent pushed to plan-rework at dev/nisse 2026-10-02 19:41:49 +00:00
7b5f0dfd18 Rework the Development Plan around live testing and the revised architecture
dev-agent closed issue dev/nisse#33 2026-10-02 19:36:54 +00:00
Add ability to reference Vikunja tickets with agent accounts.
dev-agent commented on issue dev/nisse#89 2026-10-02 19:36:54 +00:00
Gitea token is stored in the workspace clone's .git/config

Update after #90: the agent no longer keeps a workspace on its own host, and build VMs never receive the Gitea API token (D4, D7). Pushes use a key handed to that one push. This is still worth…

dev-agent commented on issue dev/nisse#30 2026-10-02 19:36:53 +00:00
Idea: one agent instance per project, with automated provisioning

Superseded by the deployment model in #90: one nisse-dev instance, with a build VM per project (Architecture X1, D3). Projects are isolated by their build VMs, not by separate agent…

dev-agent commented on issue dev/nisse#33 2026-10-02 19:36:53 +00:00
Add ability to reference Vikunja tickets with agent accounts.

Superseded by #90: Vikunja is dropped. Gitea issues are the one tracker for every agent, and ops work lives in one infrastructure repository for both sites, with site labels (Architecture L1, O5).…

dev-agent merged pull request dev/nisse#91 2026-10-02 19:36:45 +00:00
Model the agent loop as the architecture describes it
dev-agent pushed to main at dev/nisse 2026-10-02 19:36:45 +00:00
b7f1f3371c Merge pull request 'Model the agent loop as the architecture describes it' (#91) from loop-model into main
76e9fa38c7 Model the agent loop as the architecture describes it
Compare 2 commits »
dev-agent deleted branch loop-model from dev/nisse 2026-10-02 19:36:45 +00:00
dev-agent deleted branch deployment-model from dev/nisse 2026-10-02 19:36:34 +00:00
dev-agent closed issue dev/nisse#30 2026-10-02 19:36:33 +00:00
Idea: one agent instance per project, with automated provisioning
dev-agent pushed to main at dev/nisse 2026-10-02 19:36:33 +00:00
d407db72c2 Merge pull request 'Revise the deployment model: an agent host and tool VMs' (#90) from deployment-model into main
2187c24d0d Address review comments on the architecture
8c38444b88 Close five gaps the loop model found
5839091d65 Define projects as configuration entries (D8); note the agent host's recovery
4ca8e1f550 Drop Vikunja: Gitea issues are the one tracker for every agent
Compare 13 commits »