tundra

Use the `at` CLI to create, execute, monitor, and complete tasks on the Auto-Tundra daemon. Covers the full bead lifecycle from sling to done.

Use when troubleshooting build failures, test failures, daemon connectivity issues, or integration errors in Auto-Tundra.

Use the Auto-Tundra HTTP API directly (via curl) for operations not exposed in the CLI, such as task updates, terminal management, GitLab/Linear queries, and Kanban board manipulation.

Use when adding features, fixing bugs, or refactoring code in any Auto-Tundra crate. Covers build, test, lint, and validation workflows.

Use for GitHub/GitLab/Linear wiring in rust-harness to remove stub-token paths, enforce env-driven credential resolution, and add regression tests for real-client behavior with safe fallbacks.

Use for local Ollama-first execution with queued multi-agent CLI workflows. Configures auto-tundra for one-human-overseer and many-agent-subscriber code refinery mode.

Use when developing or refactoring at-cli. Runs deterministic smoke checks for run/agent/skill/doctor commands, including --dry-run and --out artifact paths.

Use for multi-lane implementation waves in rust-harness when coordinating sub-agents, sequencing risk, and enforcing compile/test gates before reporting completion.