Skip to content

grid — quick reference

First-time in a new terminal: source ~/.zshrc

Commands

grid execs     6 panes   CoS + PM + CRO + CMO + COO + CDO
grid dev       8 panes   code.platform, revenue.os, mining.mind, qa.testing, qa.visuals, qa.dataquality, qa.applications, documentation.engineering
grid ops       4 panes   sop.manager, legal.exec, security.ops, financial.research
grid rev       3 panes   sales.ops, customer.success, category.positioning
grid mktg      1 pane    category.positioning
grid qa        4 panes   qa.testing, qa.visuals, qa.dataquality, qa.applications
grid council   3 panes   CoS + PM + qa.testing

grid custom a,b,c        ad-hoc (min 2 agents)
grid list                show all presets
grid 4 | grid 6 | grid 8  legacy static grids

Convention

Execs launch once via grid execs. Team grids (dev/ops/rev/mktg) exclude their manager to avoid duplicate sessions.

Cross-dept exception (2026-04-22): grid rev includes category.positioning (CMO dept) because revenue team works with it daily. category.positioning also appears in grid mktg — if you launch both, you'll get a duplicate-session conflict on that pane. Pick one or launch grid mktg with grid custom michelle.direct-reports-minus-cp if you ever need the marketing grid without the duplicate.

Launch sequence for full 21-agent team

grid execs
grid dev
grid ops
grid rev
grid mktg

Layout after launch

  • Cmd+Shift+K — 2x2 grid (fits grid ops, grid qa)
  • Cmd+Shift+L — 2x3 grid (fits grid execs)
  • 8-pane (grid dev) — drag manually into 2x4 or 4x2
  • Command Palette → "View: Reset Editor Group Sizes" to even cells

Troubleshooting

  • grid: no workspace for size 'X' → run source ~/.zshrc (function not updated in current shell)
  • Duplicate agent panes → don't launch team grid with its manager still in grid execs
  • Terminals exit immediately → which claude should return a path

Auto-launch flow (NEW 2026-04-22)

Scheduled cron spawns the 6 Layer 1 execs at 8:00 AM PST, 7 days/week. Each cron:

  • Runs remotely (not on your Mac — cloud side), ephemeral, terminates when done
  • Posts morning check-in to #exec-checkins + per-exec channel
  • Files session-dir artifacts in the exec's memory-notes.md
  • Currently v1 (skeleton fidelity); v2 full-fidelity scoping in progress per /Claude/sessions/project.manager/cron-auto-launch-v2-scoping-2026-04-22.md

This gives execs a 1-hour buffer before the 9:00 AM weekday check-in ceiling.

Cron vs. local — critical distinction

Cron (remote) Local grid pane
Where it runs Cloud Your Mac
Persistence Ephemeral (dies on completion) Lives until you close the pane
Context Fresh each run (memory load from sources) Retains through pane life
Attachable? No — not interactive Yes
Session store ~/.claude/projects/{encoded-cwd}/ Same store — they share
Purpose Scheduled cadence posting Live work

Important: cron and local sessions for the same agent write to the same session store. A cron run at 8 AM creates a session file; a local pane opened at 9 AM with claude --continue would pick up the cron session, not last night's live session.

"I just arrived after cron ran" playbook

  1. Check Slack first. Look in #exec-checkins + your per-exec channel — cron already posted; know what it said.
  2. Read your memory-notes.md. Cron may have appended a cron-run marker entry.
  3. Decide your launch mode:
  4. Fresh pane (grid execs or grid {team}) → current default. Starts clean claude. Recommended today — your live session stands on its own.
  5. Resume prior local session → not automated yet. Manual: open a pane, cwd to your session dir, run claude --continue but be aware the latest session may be the cron, not last night's.
  6. If cron content was wrong: post a supplemental check-in to #exec-checkins with [Cron correction: ...] prefix and the corrected state. Eva's Self-SLA morning sweep handles reconciliation.

Resume vs. fresh trade-off

Fresh (grid ... default) Resume (claude --continue)
Pros Clean state; no cron contamination; predictable Continuous context across session breaks
Cons Re-reads memory each time (~20–30s startup) Can pick up the cron skeleton if cron ran more recently than last live session
When to use Default; always safe After cron v2 + session-store reconciliation rules ship (not yet)

Current recommendation: stay with fresh (grid ...). Don't add --continue to the workspace commands until cron v2 full-fidelity lands + reconciliation rules are in place (tracked in cron v2 scoping doc Section 3.5).

Files

  • Shell fn: ~/.zshrc
  • Launcher: /Claude/scripts/agents/grid-launch.sh
  • Full docs: /Claude/knowledge/tools/vscode.md + /Claude/.vscode/README.md
  • Cron v2 scoping: /Claude/sessions/project.manager/cron-auto-launch-v2-scoping-2026-04-22.md