Coder Workspaces

**Judgement** A focused and capable skill for users of the Coder platform. It exposes most of the core Coder CLI capabilities needed to manage workspaces and AI coding tasks, and emphasizes isolation by running commands *inside* Coder workspaces instead of on the host. It is best suited to teams or individuals already invested in Coder as their primary development environment. **Strengths** - Good coverage of workspace lifecycle actions (list/start/stop/restart/delete, logs, SSH). - Direct support for AI coding agents via Coder Tasks (create, connect, logs, delete). - Clear operational model that closely mirrors the official Coder CLI, reducing surprises. - Isolation of execution to Coder workspaces lowers the risk of damaging the local machine. **Key Risks / Limitations** - **Destructive actions**: `delete` for workspaces and tasks is supported and may be invoked non-interactively (e.g., `-y`), risking data loss if misused. - **External dependency**: Fully depends on a correctly configured Coder instance, CLI installation, and environment variables (`CODER_URL`, `CODER_SESSION_TOKEN`). Failures in those areas will surface as errors the skill cannot itself resolve. - **Platform-specific**: Only useful in environments where Coder is already deployed; offers little value outside that ecosystem. - **Task configuration complexity**: Template/preset handling for Coder Tasks can be confusing for less experienced users, especially when defaults are missing and interactive selection is required. **Recommended Scenarios** - Organizations that standardize on Coder workspaces for development and want AI-assistance (Claude Code, Aider, etc.) in governed, reproducible environments. - DevOps/platform teams needing a programmatic way to orchestrate and troubleshoot many Coder workspaces (e.g., starting/stopping, grabbing logs, running ad-hoc commands). - Developers who want to safely delegate code-generation or refactoring tasks to AI agents in isolated containers instead of their local machines. **Not Ideal For** - Users without an existing Coder deployment or those seeking generic local-environment management. - Highly regulated contexts where automatic deletion or modification of workspaces must be strongly guarded or additionally audited beyond what the Coder platform already provides.