Adapt For A Team
The current Hub began as a single-user local orchestrator. A team-facing distribution should separate reusable orchestration behavior from personal environment assumptions.
Sanitize First
Section titled “Sanitize First”Before sharing:
- remove personal paths
- remove private project names unless used intentionally as examples
- remove Obsidian-specific assumptions
- remove credentials and environment values
- replace local project maps with team-owned project records
- document optional adapters separately
Define Your Project Records
Section titled “Define Your Project Records”Each team should record:
- project aliases
- main worktree
- worker worktrees
- production branch
- deployment target
- local preview command
- review expectations
Decide Worker Ownership
Section titled “Decide Worker Ownership”Use owner worktrees or branches to make it clear where Codex, Claude Code, or another worker should operate. Code freshness should not silently override worker choice.
Keep Human Gates
Section titled “Keep Human Gates”Agent Hub can automate routine stages after approval, but it should still pause for:
- destructive changes
- external writes
- production deploys when policy requires explicit approval
- credential or secret changes
- infrastructure creation
- unclear product decisions
Start Small
Section titled “Start Small”Adopt in this order:
- Status and audit only.
- Controlled worker launch.
- Durable work-item queue.
- Structured worker reports.
- Hub review gates.
- Deploy orchestration.
- Team-specific adapters.