Collaboration and teams

Solo use is simple — teams need clarity on visibility and handoff.

1. Three-level identity

Rendering diagram…

Layer	Meaning	Isolation
Organization	Usually the company	Top boundary
Tenant	Business unit	Agents / KBs / skills isolated
User	Can join many tenants	Switch via top avatar

Model detail: Multi-tenancy.

2. Switching tenants

Avatar → Switch tenant.

Tenant switch

The left rail (sessions, KBs, skills, Agents) reloads under the active tenant banner.

Sessions in tenant A never appear in B. Tenant-wide KB sharing stays within the tenant — no automatic cross-tenant share; Owners migrate/copy manually when needed.

3. Roles and invites

Via Profile → Team.

3.1 Roles

Role	Create tenant	Invite/kick	Billing	Agents/KBs	Skills
Owner	✓	✓	✓	✓	✓
Normal	—	—	—	✓	✓
Invite	—	—	—	—	—

3.2 Invite flow

Rendering diagram…

4. Session collaboration

4.1 Parallel sessions

Each session owns:

Plan Mode state
Message history
Ephemeral uploads
Editor state

Left list swaps instantly; concurrent runs don’t block.

Plan Mode persists per session.

4.2 Rename / archive / delete

Action	Effect
Rename	Display name
Archive	Moved to archive bucket
Unarchive	Back to main list
Delete	Hard delete messages + ephemeral files
Clear all sessions	Danger — double confirm

Session title → Share:

Permission	Meaning
Read-only	Tenant peers view only
Collaborative	Same thread continues
Public (Owner-gated)	Anonymous view demo

4.4 Session scope

From Agent settings / Session panel:

Mode	Team hint
per-sender	One Agent per user
per-agent	Dedicated thread per Agent
shared	Handoff inside one conversation

5. Graft — cross-session handoff

combo agent lets you compose outputs across sessions via graft.

5.1 Why

Single sessions grow long → compression loses detail; parallelism and reusable artifacts suffer.

5.2 Pattern

Rendering diagram…

5.3 Usage

Compare v1.14 vs v1.17 changes.
v1.14 trace lives in {{graft:session-A-id}}.
v1.17 trace lives in {{graft:session-B-id}}.

Or /graft picker fills references. Runtime loads grafted contexts on demand.

5.4 Permissions

Default: graft your sessions plus tenant-shared ones
Cross-tenant blocked

5.5 Scenarios

Scenario	Split
Dual baseline ASPICE	A + B traces → C diff
Code review splits	Per-module reviewers → merge report
Patent drafting	Research session → drafting session grafts conclusions

See ASPICE engineering loop.