lfg2025/archy
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

docs: record implemented session execution slice

Browse Source
This commit is contained in:
archipelago
2026-10-09 07:32:31 -04:00
parent 16085c723a
commit f50521072d
1 changed files with 17 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/terminal-developer-environment-spec.md
+17 -2
View File
@@ -1,7 +1,9 @@
# Archipelago terminal and developer environment plan # Archipelago terminal and developer environment plan
Status: planning draft, 2026-10-09. No runtime implementation or installation is Status: execution draft, 2026-10-09. The local persistent-session primitive is
part of this change. Repository baseline: `2cb1bae5ce244d387679f90951d62fd030ebf228`. implemented in `scripts/archy-session`; dashboard/WebSocket attachment,
developer-account provisioning, and Codex installation remain follow-on slices.
Repository baseline: `2cb1bae5ce244d387679f90951d62fd030ebf228`.
Archipelago should let an owner open a real terminal, resume previous work, Archipelago should let an owner open a real terminal, resume previous work,
configure their system, and ask a preinstalled coding agent to build an app that configure their system, and ask a preinstalled coding agent to build an app that
@@ -163,6 +165,19 @@ has normal shell semantics. Focus can move to toolbar controls and back.
## Persistent sessions and one-click resume ## Persistent sessions and one-click resume
### Implemented local primitive
`scripts/archy-session` provides the first execution slice for named sessions.
It stores atomic JSON metadata under the user state directory and uses one
isolated tmux session per workspace. `list` reconciles metadata with the live
tmux process, `attach` resumes an existing process without creating a duplicate,
`rename` preserves the workspace, and `end` is the only operation that stops a
session. Its lifecycle test is `scripts/tests/archy-session-test.sh`.
This helper is intentionally not the browser security boundary: the future
session service must enforce owner/node/boot identity, attachment grants, CSRF,
and revocation before exposing it through the dashboard.
This is a core release criterion, including the first usable terminal milestone. This is a core release criterion, including the first usable terminal milestone.
Session execution lives on the node in a dedicated, supervised user environment. Session execution lives on the node in a dedicated, supervised user environment.