claude-code
470d826c10
werkator build succeeded after 01:56
Co-authored-by: claude-code <claude-code@javagil.de>
44 lines
2.3 KiB
Markdown
44 lines
2.3 KiB
Markdown
# PR#57: A Plan for Werkregie Satellites
|
|
|
|
> **WARNING:** This document describes only the change applied in this PR.
|
|
> It may already be outdated once the next PR is merged.
|
|
> Historic PR documentation is not maintained along with new PRs; treat it as a snapshot.
|
|
|
|
## Problem
|
|
|
|
An account in which coding agents work needs many tools, logins, secrets and services.
|
|
Today the user sets each of them up by hand, and nothing records what it needs.
|
|
A freshly installed account takes hours until agents can work in it, and steps get forgotten.
|
|
|
|
The user wants Werkregie to set up such an account almost completely, as an extension of the relay mode.
|
|
Such an account is a satellite: it reads its agents for the server, and later it also acts on them.
|
|
A client is a dashboard the user operates.
|
|
|
|
## Non-Goals
|
|
|
|
- No code; this PR records what a satellite needs and plans the steps.
|
|
- No server-side setup; the hosts of Werkator, werkrevisor and the Werkregie server stay as they are.
|
|
|
|
## Solution
|
|
|
|
- `doc/satellite-inventory.md`: what `think` has today, grouped by component.
|
|
- `#sat` in `doc/werkregie.werkbaum`: the plan in steps, each step one PR.
|
|
- Version 0.35.4.
|
|
|
|
## Open Questions
|
|
|
|
- [x] Own idempotent steps in Kotlin, or Ansible, Nix or chezmoi?
|
|
Own steps in Kotlin, decided by mi on 2026-10-13: no new technology, and the state goes straight into the dashboard.
|
|
- [x] Where do the secrets come from: end-to-end from the main account, or an encrypted store on the server?
|
|
End to end from the main account, decided by mi on 2026-10-13: the server sees only ciphertext.
|
|
- [x] Do the agents get a Linux account of their own on `think`?
|
|
The setups differ, decided by mi on 2026-10-13: another Unix account, a local or remote virtual machine, the agent as user or root;
|
|
the satellite assumes none of them.
|
|
- [x] Does a satellite get the memory of Claude Code?
|
|
No, decided by mi on 2026-10-13: knowledge of the processes belongs into the agentic workflow,
|
|
and a customer's memory is not shared.
|
|
- [x] Claude Desktop or the Claude Code CLI on a satellite, and how does the user see a frontend the agent builds there?
|
|
Claude Desktop on an Omarchy Linux desktop, reached over RDP, decided by mi on 2026-10-13;
|
|
the user moves to Omarchy Linux altogether in the medium term.
|
|
Agents on the CLI alone are an experiment for later.
|