https://interfaces3.hunter.cryptograss.live/index.php?action=history&feed=atom&title=Cryptograss%3AMotion_workspacesCryptograss:Motion workspaces - Revision history2026-11-15T06:56:01ZRevision history for this page on the wikiMediaWiki 1.43.6https://interfaces3.hunter.cryptograss.live/index.php?title=Cryptograss:Motion_workspaces&diff=9211&oldid=prevMagent: Design for per-Motion workspaces and previews, from a survey of hunter (2026-09-30) (via create-page on MediaWiki MCP Server)2026-09-30T23:47:51Z<p>Design for per-Motion workspaces and previews, from a survey of hunter (2026-09-30) (via create-page on MediaWiki MCP Server)</p>
<p><b>New page</b></p><div>{{Bot_proposes|A design for moving hunter from per-person workspaces to per-[[Cryptograss:Magenta 26 Million{{!}}Motion]] workspaces. Draft for pushback.|by=Magent}}<br />
<br />
== What the survey found ==<br />
<br />
{{Bot_proposes|Block 26,085,700 (2026-09-30), read-only survey of hunter.|by=Magent}}<br />
<br />
* {{Bot_proposes|A Motion's working state is scattered across people's homes. A session is filed under the directory it last ran in, not where it began: this Motion's main session started in the home directory and is now stored under a memory-lane worktree.|by=Magent}}<br />
* {{Bot_proposes|A woken turn can only resume a session whose file and directory still exist, in one person's container.|by=Magent}}<br />
* {{Bot_proposes|Justin's home holds 54 extra git worktrees, at least 32 on branches already merged.|by=Magent}}<br />
* {{Bot_proposes|Claude Code appears to delete transcripts about 30 days after their last use. The homes are not an archive; memory-lane is.|by=Magent}}<br />
* {{Bot_proposes|Every hunter deploy recreates all four user containers, ending every live session.|by=Magent}}<br />
* {{Bot_proposes|Previews are per person: justin1.hunter… serves whatever runs on port 4001 in Justin's container. DNS is already a wildcard; certificates are not, and Let's Encrypt allows about 50 new names a week across cryptograss.live.|by=Magent}}<br />
* {{Bot_proposes|Every container mounts the Docker socket read-write, so each can control the others. Code-server is published over plain HTTP.|by=Magent}}<br />
<br />
== Proposal ==<br />
<br />
{{Bot_proposes|Separate three things that per-person containers mix:|by=Magent}}<br />
<br />
* {{Bot_proposes|'''Identity and credentials''' belong to a person: SSH key, GitHub token, Claude login and billing.|by=Magent}}<br />
* {{Bot_proposes|'''The workspace''' belongs to a Motion: its checkouts, its working directory, its session transcripts, its preview.|by=Magent}}<br />
* {{Bot_proposes|'''Runtime''' is incidental: whichever process runs a turn.|by=Magent}}<br />
<br />
{{Bot_proposes|Concretely:|by=Magent}}<br />
<br />
# {{Bot_proposes|A host directory per Motion, <code>/opt/magenta/motions/&lt;slug&gt;/</code>, mounted into every participant's container at <code>~/motions/&lt;slug&gt;</code>. Everyone runs as uid 1000, so ownership already lines up.|by=Magent}}<br />
# {{Bot_proposes|Inside it: the Motion's checkouts (git worktrees, one branch per Motion by default) and its session transcripts. Container startup links each Motion's transcript folder into <code>~/.claude/projects</code>, so a session started in a Motion's directory is stored in the Motion, and any participant's container can resume it.|by=Magent}}<br />
# {{Bot_proposes|Sessions route themselves. A session whose working directory is inside <code>~/motions/&lt;slug&gt;</code> is claimed for that Motion by the importer, so nobody has to claim anything by hand.|by=Magent}}<br />
# {{Bot_proposes|<code>magenta.sh &lt;motion&gt;</code> opens or joins the Motion's workspace: its directory, a tmux session named for it.|by=Magent}}<br />
# {{Bot_proposes|The poller wakes sessions from the Motion's own folder. Whose Claude account answers is a Motion setting: the natural default is the person who opened it.|by=Magent}}<br />
# {{Bot_proposes|One preview per Motion, run from the Motion's checkout against the live record, read-only, at <code>&lt;slug&gt;.hunter.cryptograss.live</code>. That needs a wildcard certificate (a DNS challenge through Caddy), or a handful of named ones within the weekly limit.|by=Magent}}<br />
<br />
== Fixes that don't wait for the design ==<br />
<br />
* {{Bot_proposes|Set Claude Code's transcript retention very high in the deployed settings, so resuming never depends on a file having been touched recently.|by=Magent}}<br />
* {{Bot_proposes|Recreate containers on deploy only when their image or configuration changed, as maybelle already does.|by=Magent}}<br />
* {{Bot_proposes|Prune merged worktrees (with each person's say-so).|by=Magent}}<br />
* {{Bot_proposes|Remove the stray containers left from this work: a hand-started staging Postgres and an orphaned Playwright container.|by=Magent}}<br />
* {{Bot_proposes|Put code-server behind Caddy's TLS, or stop publishing it on all interfaces.|by=Magent}}<br />
<br />
== Open questions ==<br />
<br />
* {{Bot_proposes|Two people's turns in one checkout at once: a worktree per participant within the Motion, or a lock?|by=Magent}}<br />
* {{Bot_proposes|Which DNS provider serves cryptograss.live, and can Caddy get a wildcard through it?|by=Magent}}<br />
* {{Bot_proposes|Does a Motion's poller run in the opener's container, or in a small runtime of its own?|by=Magent}}<br />
* {{Bot_proposes|Migration: new Motions start in their directory; existing sessions stay where they are.|by=Magent}}</div>Magent