heavy-duty/box
7
0
Fork 1
Code Issues 9 Pull requests Projects Releases 4 Packages Wiki Activity Actions

docs: make the box narrative agent-agnostic, not Claude-specific #58

Merged
dan-claude-bot merged 3 commits from docs/agnostic-readme into main 2026-07-15 00:24:44 +00:00
Conversation 0 Commits 3 Files changed 4 +63 -51
dan-claude-bot commented 2026-07-15 00:16:07 +00:00 (Migrated from github.com)
Copy link

What

The docs told box's story around Claude Code even though the tool already ships codex and grok templates and treats every coding agent identically. This reframes the generic prose to speak of "the coding agent" while keeping claude as the named, concrete example — it's the flagship and where the project started, so it stays in intros, login walk-throughs, and template tables.

Files

README.md

  • Intro leads with the coding-agent templates (claude/codex/grok) instead of a single flagship; "no Claude token" → "no agent token".
  • .box/ runbook read by "the box's coding agent".
  • Quick start: pick any agent template; keeps the claude login walk-through as the worked example.
  • Templates: "No coding agent is special"; snapshots "agent login"; isolation trust boundary holds "the coding agent"; non-goals "ask the agent".

docs/box-recipe.md

  • .box/ convention framed around whichever agent the box was minted with.
  • Names the per-template context file (~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, ~/.grok/AGENTS.md) instead of hardcoding Claude's.
  • "instructions to the agent", "the agent reads it top to bottom", "let the agent infer".

docs/box-design.md

  • "VMs with a coding agent installed"; "The agent (Claude Code, Codex, Grok — whichever template)"; "no agent credentials"; auth example generalized (claude/codex/grok each have a login step); global context file named per template.

drill/README.md

  • "does not check" note: the drill confirms each coding-agent template's CLI is installed and runnable, not just Claude Code.

Deliberately left untouched

  • Legacy isolation-stack identifiers — claudenet, claude-dev, claude-isolate, user.claudebox. Literal names honored forever, not narrative.
  • The claude template files — user claude, /home/claude/… paths, claude --version probes.
  • drill/RUNS.md — historical run log.

No behavior, command, or flag changes — docs only.

docs/box-design.md (also updated here)

  • Renamed the isolation-stack references in the Snapshots, ownership-rule, and Isolation sections from the pre-0.4.0 names (claudenet/claude-dev/claude-isolate) to the current boxnet/box-net/box-isolate, matching the README, host/setup-host.sh, and host/box-firewall.sh. Stale wording only — the mechanism is unchanged.

🤖 Generated with Claude Code

## What The docs told box's story around Claude Code even though the tool already ships `codex` and `grok` templates and treats every coding agent identically. This reframes the **generic prose** to speak of "the coding agent" while keeping `claude` as the **named, concrete example** — it's the flagship and where the project started, so it stays in intros, login walk-throughs, and template tables. ## Files **`README.md`** - Intro leads with the coding-agent templates (`claude`/`codex`/`grok`) instead of a single flagship; "no Claude token" → "no agent token". - `.box/` runbook read by "the box's coding agent". - Quick start: pick any agent template; keeps the `claude` login walk-through as the worked example. - Templates: "No coding agent is special"; snapshots "agent login"; isolation trust boundary holds "the coding agent"; non-goals "ask the agent". **`docs/box-recipe.md`** - `.box/` convention framed around whichever agent the box was minted with. - Names the per-template context file (`~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, `~/.grok/AGENTS.md`) instead of hardcoding Claude's. - "instructions to the agent", "the agent reads it top to bottom", "let the agent infer". **`docs/box-design.md`** - "VMs with a coding agent installed"; "The agent (Claude Code, Codex, Grok — whichever template)"; "no agent credentials"; auth example generalized (`claude`/`codex`/`grok` each have a login step); global context file named per template. **`drill/README.md`** - "does not check" note: the drill confirms *each* coding-agent template's CLI is installed and runnable, not just Claude Code. ## Deliberately left untouched - **Legacy isolation-stack identifiers** — `claudenet`, `claude-dev`, `claude-isolate`, `user.claudebox`. Literal names honored forever, not narrative. - **The `claude` template files** — user `claude`, `/home/claude/…` paths, `claude --version` probes. - **`drill/RUNS.md`** — historical run log. No behavior, command, or flag changes — docs only. **`docs/box-design.md`** (also updated here) - Renamed the isolation-stack references in the Snapshots, ownership-rule, and Isolation sections from the pre-0.4.0 names (`claudenet`/`claude-dev`/`claude-isolate`) to the current `boxnet`/`box-net`/`box-isolate`, matching the README, `host/setup-host.sh`, and `host/box-firewall.sh`. Stale wording only — the mechanism is unchanged. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
blocked

Waiting on another PR or issue to land first

  
blocker:ci-red

A check is failing — the agent owes a fix (not a rebase)

  
blocker:conflict

Does not merge — the branch conflicts and the agent owes a rebase

  
blocker:drill-pending

Release ceremony is correct but has no drill record yet

  
blocker:unrequested

Somebody still owes a verdict and nobody was asked for one

  
bug

Something isn't working

  
claimed

a builder owns it: assignee set, a draft PR expected shortly

  
documentation

Improvements or additions to documentation

  
enhancement

New feature or request

  
epic

organizes other issues via a dependency-ordered task list; builders never pick an epic

  
merge-next

Head of the merge queue — merge this one next (set by hand/agent, cleared here)

  
needs-triage

an issue that did not come through triage — owes normalization or conversion back to a discussion

  
ready

triaged, spec complete, unblocked — a builder can start now and succeed

  
release

Release flow and version/packaging work

  
scope:cli

bin/box — the command surface

  
scope:drill

drill/ — rehearsals, doctor, RUNS.md

  
scope:host

host/ — setup, teardown, firewall, isolation stack

  
scope:installer

install.sh, versioned installs, upgrade/uninstall

  
scope:templates

templates/ — the box seeds

  
scope:tiers

restricted tier — grant/revoke, multi-user

  
stale

No activity for 48h — needs a poke (sweep-managed)

  
state:addressing

All bots reviewed — coding agent owes the single reply + fixes

  
state:bots-reviewing

Waiting on the bot reviewers to finish the round

  
state:building

PR is a draft — the coding agent is still building

  
state:needs-human

No blockers, all bots approve — waiting on the human reviewer

No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:cli
scope:drill
scope:host
scope:installer
scope:templates
scope:tiers
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/box#58
No description provided.
Delete branch "docs/agnostic-readme"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?