Adaptive task orchestration for OpenCode — focused workers, verified changes and project-local control.
Русский README · Releases · Changelog
TeamLead helps turn a development goal into a checked change. It selects an execution strategy, assigns bounded work, runs deterministic checks and integrates verified patches. Its objective is the fastest verified correct result at the lowest practical model cost.
- Adaptive execution: Direct, Managed or Team, depending on the task.
- Model selection: role assignments and pools, provider availability, context/tool capabilities, cost and recorded outcomes.
- Bounded workers: explicit read/write scopes, isolated Git worktrees and verification before integration.
- Project-local settings and history: independent budgets and execution records even with a global installation.
- OpenCode integration: slash commands, live status near the prompt and a TeamLead section in Ctrl+P when TUI plugins are supported.
- English and Russian: installer prompts and TeamLead UI localization.
- Scoped removal: dedicated uninstallers preserve unrelated OpenCode files and independent local installations.
| Mode | Workflow |
|---|---|
| Direct | One bounded worker, affected checks and risk-based review. |
| Managed | Structured execution with targeted verification and conditional review. |
| Team | A Lead builds a task graph; non-conflicting workers execute in parallel, followed by verification and review. |
TeamLead selects the smallest useful orchestration depth. More workers are used only when they can improve the verified outcome.
See compatibility and requirements. Download and extract a release archive, or use a local checkout. Run the installer from the distribution root.
.\install.ps1bash ./install.shThe menu lets you choose the language, local installation in a project or global installation for the current user. Local installation asks for the project directory.
For unattended installation:
.\install.ps1 -InstallScope Local -Project C:\projects\my-app
.\install.ps1 -InstallScope Global -Language enbash ./install.sh --scope local --project /path/to/my-app
bash ./install.sh --scope global --language enRestart OpenCode after installation. Global installation shares code, agents and commands; settings and history stay within each project. Detailed Russian instructions: INSTALL_RU.md.
Open OpenCode in your project and run:
/lead-doctor
/lead-models
/lead-settings
/lead-plan Fix the authentication bug and add a regression test
Inspect the plan, then start execution:
/lead Fix the authentication bug and add a regression test
Use a Git repository for mutating tasks. Configure your model provider in OpenCode before executing model-backed work.
| Command | Purpose |
|---|---|
/lead |
Execute a development goal. |
/lead-plan |
Preview the execution strategy and tasks. |
/lead-status |
Show execution status and history. |
/lead-resume |
Continue an eligible unfinished run. |
/lead-models |
Inspect connected models and role assignments. |
/lead-settings |
Configure strategy, models, concurrency, budgets and review. |
/lead-doctor |
Check host capabilities and installed files. |
The optional Ctrl+P menu provides shortcuts to the same workflows.
.opencode/teamlead.json— project settings..opencode/.teamlead/— history, evidence, locks, patches and temporary worktrees..teamlead-projects/in the global configuration directory — projects registered by the global plugin.
Settings include the execution strategy, role models/pools, provider concurrency, token/cost admission budgets and review depth. See budgeting and state and recovery.
Close OpenCode and run the uninstaller from the distribution root:
.\uninstall.ps1bash ./uninstall.shChoose local or global scope. Local removal cleans TeamLead code, settings, history, TUI registration and owned Git worktrees. Global removal also cleans registered projects' TeamLead data, while preserving independent local installations and their data. Unrelated plugins, commands and JSONC comments are preserved.
Only registered projects are included in global cleanup. Use local removal for any other project you want to clean.
Worker output is untrusted: paths and patches are checked before integration. Git worktrees isolate filesystem changes, not processes. Repository checks execute with the host user's privileges; use TeamLead with repositories you trust.
See architecture, threat model and testing for the implemented guarantees and verification limits.
MIT © demyanovvvv.