Collaborators and working environments
Define who handles a task and where that work takes place.
Agent kinds define focused collaborators
A custom agent kind supplies instructions, a tool selection, and a permission mode for a subagent. A documentation researcher and a code-editing implementer should not necessarily receive the same tools or authority.
Separate investigation from implementation
Give a researcher reading and search tools to investigate a problem and return findings. Give an implementer editing tools for the fix. The agent kind supplies the role and tool selection; permission rules determine which operations are allowed.
Worktree sessions are independent working contexts
A worktree session has its own checkout and branch. It is not simply another name for a short-lived subagent. Use it when parallel work needs an isolated source tree and a longer-lived session.
Prepare the environment as well as the branch
Worktree environment configuration and lifecycle hooks can arrange project-specific services, ports, and setup or teardown. A separate checkout alone does not isolate databases or external resources; the project must configure those.
Run independent changes side by side
A frontend change and an API change can live in separate worktree sessions, each on its own branch. Environment configuration can assign their services separate ports. Both sessions can reuse the same skills while working on different outcomes.