Current behavior
first-tree context enable --provider … --team … is the BYO entry point. It (a) validates server-side that the signed-in member belongs to the Team and that the checkout's repository is inside the Team's active code-repository scope, (b) installs the user-scope provider plugin (once per machine per provider), and (c) records the exact checkout→Team binding. It does not create Team membership — that comes from the invite flow.
Problem
The name reads like toggling a machine feature, while what the user is conceptually doing is joining a Team's context with their own coding agent. As BYO grows beyond Context (more capabilities for bring-your-own agents), the entry verb should say what the user is doing, not which subsystem is touched.
Proposal (product-shape discussion)
Reshape the BYO entry into an explicit team-join command — e.g. first-tree team join <team-id> (exact naming open) — that performs today's enable semantics underneath and leaves room for future BYO capabilities to hang off the joined state. Keep the layered lifecycle (status / repair / disable) and the exact-checkout binding model unchanged. context enable can remain as an alias during migration.
Per the BYO join-prompt improvement discussion (2026-07-30): context enable stays unchanged for now; this issue tracks the reshape.
Current behavior
first-tree context enable --provider … --team …is the BYO entry point. It (a) validates server-side that the signed-in member belongs to the Team and that the checkout's repository is inside the Team's active code-repository scope, (b) installs the user-scope provider plugin (once per machine per provider), and (c) records the exact checkout→Team binding. It does not create Team membership — that comes from the invite flow.Problem
The name reads like toggling a machine feature, while what the user is conceptually doing is joining a Team's context with their own coding agent. As BYO grows beyond Context (more capabilities for bring-your-own agents), the entry verb should say what the user is doing, not which subsystem is touched.
Proposal (product-shape discussion)
Reshape the BYO entry into an explicit team-join command — e.g.
first-tree team join <team-id>(exact naming open) — that performs today's enable semantics underneath and leaves room for future BYO capabilities to hang off the joined state. Keep the layered lifecycle (status/repair/disable) and the exact-checkout binding model unchanged.context enablecan remain as an alias during migration.Per the BYO join-prompt improvement discussion (2026-07-30):
context enablestays unchanged for now; this issue tracks the reshape.