Camp's git-native, mission-oriented context workspaces become an adopted primitive for managing persistent, multi-project agent context across sessions and machines.

state: seedheat: lowuncertainty: highknownscott: lowagent-memory agent-orchestration developer-tools context-workspaces git-native cross-machine-syncObedience-Corplancekrogers

What is this?

Camp is a CLI tool (by Obedience-Corp / lancekrogers) that creates version-controlled context workspaces in git, organized around 'missions', with shell integration and cross-machine sync via Tailscale. The web snippets do not directly describe Camp — they cover the broader repo-native context trend (Storybloq's three-camps piece, the Git-Context-Controller paper, GitHub's agent workspace direction, and a handful of related tools). The evidence titles are the only source confirming Camp's specific feature set; the web results confirm the category is active but do not validate Camp's adoption or differentiation.

Why it matters to Scott

Scott's own canon already carries this position end-to-end — Markdown OS (git-native folder-as-agent), Cognitive Git's layered commit history, and long-running-agents' durable-external-state doctrine all predate and argue this exact design — and the radar already tracks a dozen sibling git-native/cross-machine context tools (MemTether, Slivingdoc, Agentgit, Memctl, Zuse, AgentLane, Caffold), so Camp is another instance of an established pattern, not a new claim on either side. The only mildly distinctive elements — 'missions' as the workspace unit echoing his Goal-World Isolation / One-Task Rule, and Tailscale-based sync matching his own stack (dev:technology.tailscale, search-conversations archive) — make it worth folding into the existing category page rather than treating as news.

ip:framework.markdown-osip:source.markdown-as-an-operating-system-ebookip:concept.goal-world-isolationip:framework.long-running-agentsdev:concept.resumable-agent-job-control-planedev:technology.tailscaleradar:memtether-symlink-shared-agent-memoryradar:slivingdoc-git-s3-agent-memoryradar:memctl-versioned-agent-memoryradar:agentgit-accountless-agent-handoffsradar:agentlane-git-native-coordinationradar:caffold-cross-device-workspace

queries asked of Scott's wikis

agent memory persistence across sessions and machines
git-native context workspace primitives for agents
cross-machine sync for agent context (Tailscale, git remotes)
mission-oriented task decomposition in agent workflows
developer tooling for agent context versioning and handoff
Obedience-Corp or lancekrogers prior work on agent infrastructure

Measured heat

now 0 pts/hpeak 2 pts/hcomments 0/hpeers p26momentum: steady2 platformsage 99h

points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

10-07 13:00	⭐ origin echo-reconstructed	CLI tool for managing multi-project context workspaces in git with missions, shell integration, cross-machine sync via Tailscale. Obedience-Corp on github (echo) · attributed from hn.story.50012726	—
10-08 21:40	first on hacker news · published · +32.7h	Show HN: Camp version controlled context workspaces lancekrogers	—
10-08 21:40	amplified on hacker news	hn.story.50012726 lancekrogers	peak 1 · 0 comments · 35% of case engagement
10-11 13:58	amplified on hacker news 👑	hn.story.50043372 Na6z	peak 1 · 1 comments · 65% of case engagement
10-08 22:33	our radar first saw it · +33.5h	discovery anchor: hn.story.50012726	—

pace: p9 vs 1247 stories at the 96h mark (now 99h old) — behind 3jsbench-llm-3d-generation-benchmark (0.5x)

Evidence (3) — ⭐ canonical anchor

source	object	author	score	comments
🟧 hn	Show HN: Camp version controlled context workspaces	lancekrogers	1	0
🟧 echo.github ⭐	CLI tool for managing multi-project context workspaces in git with missions, shell integration, cross-machine sync via Tailscale.	Obedience-Corp	—	—
🟧 hn	Show HN: Git for Robots In The Future	Na6z	1	1

Interpretation history

2026-10-11T16:00:12Z
Camp's own HN post remains at 1 upvote/0 comments after ~3 days; the attached 'Git for Robots' signal is a related category signal but does not validate Camp's adoption. The git-native context workspace pattern is established in Scott's canon and across a dozen sibling tools — Camp has not yet differentiated or gained traction.
2026-10-11T15:42:37Z
evidence attached: hn.story.50043372 — 'Git for Robots' project signals git-native workspace patterns for autonomous agents, directly pertinent to the case's hypothesis about git-native context workspaces becoming an adopted primitive.
2026-10-09T01:34:26Z
grounded: known/low — Scott's own canon already carries this position end-to-end — Markdown OS (git-native folder-as-agent), Cognitive Git's layered commit history, and long-running-
2026-10-09T01:26:08Z
case created — CLI tool for version-controlled context workspaces with 'missions', shell integration, and cross-machine sync — directly addresses agent memory/workspace continuity, a hot topic.

Decision trace

10-12 03:00repriceCamp's own HN post remains at 1 upvote/0 comments after ~3 days; the attached 'Git for Robots' signal is a related category signal but does not validate Camp's adoption. The git-na
10-12 02:50attention_routeThe editor compared this story and chose to keep watching.
10-12 02:42attention_candidateattach
10-12 02:42attach'Git for Robots' project signals git-native workspace patterns for autonomous agents, directly pertinent to the case's hypothesis about git-native context workspaces becoming an adopted
10-12 02:41propose_attach'Git for Robots' project signals git-native workspace patterns for autonomous agents, directly pertinent to the case's hypothesis about git-native context workspaces becoming an adopted
10-09 13:18attention_routeThe editor compared this story and chose to keep watching.
10-09 13:11attention_candidatecreate
10-09 12:34groundScott's own canon already carries this position end-to-end — Markdown OS (git-native folder-as-agent), Cognitive Git's layered commit history, and long-running-agents' durable-external-
10-09 12:26createCLI tool for version-controlled context workspaces with 'missions', shell integration, and cross-machine sync — directly addresses agent memory/workspace continuity, a hot topic.