Repository navigation
Collab 2.0.0 — Observable collaboration and live settings
Collab 2.0 keeps collaboration moving while protecting the coding agent’s attention. Scoped conversation workers exchange routine messages; the main agent receives coalesced decisions and recovery notices. Runtime state lives outside repositories and is isolated by workspace, agent and session.
Breaking upgrade
Upgrade both host and guest to stable 2.x and restart the hub. Hosts reject pre-v2 guests, including saved-token reconnections; guests check the host before sending invites or saved credentials. Refresh installed guidance with collab skills install. Back up persistent state before upgrading; legacy repo-local state is never silently claimed.
What changed
- Native conversation-worker adapters for Codex, Claude, OpenCode and Cursor, with configurable model defaults, budgets, deadlines and local guidance.
- A keyboard/mouse settings TUI (
collab config --tui) alongside existing CLI settings. Operational changes reload at the next relevant operation. - Expandable participant details for model, context, quotas, costs, native subagents and separate conversation-worker usage. Visible fields and price maps are configurable; unsupported or stale data stays explicit.
- Provider telemetry normalization using explicit native snapshots, source/freshness labels and conditional teammate-capacity estimates.
- Explicit skill publication, inventory, inspection and withdrawal, with no automatic execution or installation.
- Revised agent rules for goal/acceptance checks, clear ownership, bounded delegation, validation and evidence-based handoffs.
- Fixes for #84–#86: accepted text is preserved, overflow reconnects instead of dropping history, bounded private-history replay repairs visible gaps, and fresh CLI processes retain the correct agent identity.
- Bounded telemetry subprocess output, deadlines and process-group cleanup.
- Updated README, installation and agent guides, protocol, CLI reference, architecture diagram and three real terminal screenshots.
Validation and measurements
3,532 tests passed in the final full suite (209.57 s), including private HTTP/SSE and real ncurses/tmux keyboard/mouse interaction. An additional focused run passed 119 compatibility, recovery, terminal and documentation checks. Wheel and sdist build and package-content checks passed. Independent challenger findings are fixed; synthetic real host/guest chat, skill sharing and quota-capacity scenarios passed. Provider CLIs were not exercised with billed/live credentials.
A 20,000-event instrumented soak ended at 34,884 KiB RSS with stable descriptors and no retained Python heap growth; 79.322 seconds wall / 17.677 seconds CPU. Twelve-second idle samples used 0.667% of one core for the viewer and 0.333% for settings. Flooding/silent subprocess probes stayed bounded. These are synthetic workload measurements, not a universal leak-free or provider-performance guarantee; the viewer’s separate allocation investigation is documented.
See the v2 guide, settings, telemetry sources and limits, and performance report.