31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
# PR#87: A Spike Plans T3 Code between Werkregie and the Agents
|
|
|
|
Version: patch
|
|
|
|
> **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
|
|
|
|
The user wants to work from one central place and operate satellites remotely, one per customer or field.
|
|
A satellite is not trusted: it reports to the main account, but sees nothing of it or of other satellites.
|
|
Claude Desktop on a satellite shows all sessions of the user's account, and Werkregie cannot open a session on another machine.
|
|
T3 Code is an open control surface for agent CLIs with one server per machine; it may solve a part of this.
|
|
|
|
## Non-Goals
|
|
|
|
- No code; the plan only.
|
|
- No decision for T3 Code as a technology; the spike prepares it.
|
|
|
|
## Solution
|
|
|
|
- `doc/werkregie.werkbaum`: the node `#sat.t3` with the steps of the spike, and the block `#sat.t3` with the analysis:
|
|
a remote satellite and an agent of another Unix user on the same laptop, the isolation, links, MCP, the author in transcripts,
|
|
Gitea, and the decision between taking over functions of T3 Code and working with it as the hub.
|
|
- The plan records the finished moves of werkator (werkator PR#163) and werkbaum (werkbaum PR#11) to `de.javagil`.
|
|
|
|
## Open Questions
|
|
|
|
None.
|