Skip to content

[DRAFT] chore(coder-labs/templates/tasks-docker): remove the Tasks on Docker template - #1045

Open
david-fraley wants to merge 6 commits into
mainfrom
dfraley/remove-tasks-docker-template
Open

[DRAFT] chore(coder-labs/templates/tasks-docker): remove the Tasks on Docker template#1045
david-fraley wants to merge 6 commits into
mainfrom
dfraley/remove-tasks-docker-template

Conversation

@david-fraley

@david-fraley david-fraley commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Related: coder/coder#28008, which deprecates Coder Tasks as of Coder v2.36, hides it behind the internal CODER_ENABLE_AI_TASKS flag, and removes the Tasks docs and the equivalent in-repo example template.

Removes the coder-labs/tasks-docker template and the Coder Tasks guidance that pointed at it.

The template exists only to demo Coder Tasks: it declares coder_ai_task and reads data "coder_task". On a v2.36 deployment with default settings the Tasks UI, /tasks routes and Tasks API are unavailable, so the template has no working entry point.

Changes

  • Delete registry/coder-labs/templates/tasks-docker/ (README.md, main.tf).
  • Delete registry/coder-labs/.images/tasks-screenshot.png, which only that README used.
  • .agents/skills/coder-templates/SKILL.md: drop the Coder Tasks guidance, so the skill stops teaching agents to build templates against a deprecated feature.
    • the Tasks docs link,
    • the coder_ai_task resource and coder_task data source rows in the provider tables,
    • the whole ### Task-Oriented Templates section.
    • The Task column header in the Commands table stays; it is a plain table heading, not Coder Tasks.
  • registry/sharkymark/templates/docker-claude/README.md: remove the link to the deleted main.tf and the dead coder.com/docs/ai-coder/tasks link. That template never declared coder_ai_task, so Tasks docs were the wrong reference for it regardless.
  • registry/coder/modules/claude-code/README.md and registry/coder-labs/modules/codex/README.md: in the v5 upgrade warning, unlink the deleted Tasks docs page. In claude-code, "We plan to add those back in a follow-up" becomes "We plan to add Boundary support back in a follow-up", since Tasks support is not coming back.
  • registry/harleylrn/modules/kiro-cli/README.md: unlink the same deleted page. Nothing else changes there; see below.

Docs-only, so no module version bumps.

Effect

The template disappears from registry.coder.com. Anyone who already created a Coder template from it is unaffected; template versions live in their own deployment, not here.

Not in this PR

  • Changing kiro-cli's Coder Tasks support. The module implements it for real: a report_tasks input, a task_app_id output, ai_prompt wiring and MCP task reporting baked into its default system prompt. Removing the integration means changing the module and releasing a new version, which would break existing consumers on Coder versions where Tasks still works. Only the dead docs link is fixed here.
  • Coder Tasks tags and "task reporting" wording in module frontmatter and descriptions, which affect registry search.
  • .icons/tasks.svg, kept in case anything external references it.

Validation

  • go build ./cmd/readmevalidation && ./readmevalidation: passes, all relative README URLs still valid.
  • bun x prettier --check .: passes.

Authored by Coder Agents on behalf of @david-fraley.

…template

Coder Tasks is deprecated as of Coder v2.36 and is hidden by default, so
this template cannot be used on a default deployment. Remove the template,
its orphaned screenshot, and the two references that pointed at it.
@@ -27,8 +27,6 @@ An experimental AI agent integration with Claude CodeAI agent

[Coder docs on AI agents and tasks](https://coder.com/docs/ai-coder/tasks)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this also needs to go or updated.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed in 66e60dd. That page is deleted in coder/coder#28008, so there is nothing accurate to point it at for this template: docker-claude does not declare coder_ai_task, so Tasks docs were the wrong reference even before the deprecation. The remaining links in Resources cover the module and providers.

The same dead link still exists in .agents/skills/coder-templates/SKILL.md and in the claude-code, codex and kiro-cli module READMEs. I left those out because they are not just dead links: they document actual Tasks support in those modules, so deciding what replaces them is a product call rather than a cleanup. Happy to fold that into this PR if you would rather do it in one pass.

Reply generated by Coder Agents on behalf of @david-fraley.

Comment thread registry/sharkymark/templates/docker-claude/README.md Outdated
@david-fraley david-fraley changed the title chore(coder-labs/templates/tasks-docker): remove the Tasks on Docker template [DRAFT] chore(coder-labs/templates/tasks-docker): remove the Tasks on Docker template Aug 11, 2026
@matifali
matifali marked this pull request as draft August 11, 2026 16:41
@linear-code

linear-code Bot commented Aug 18, 2026

Copy link
Copy Markdown

REG-78

…warnings

Coder Tasks is deprecated as of Coder v2.36. Remove the Tasks docs links,
the coder_ai_task and coder_task provider entries, and the task-oriented
templates section from the templates skill. In the claude-code and codex
upgrade warnings, unlink the deleted Tasks docs page and scope the follow-up
promise to Boundary only.
@github-actions

github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Module Scorecard Check

coder/claude-code: 64 → 64

Score unchanged at 64 / 100. This PR does not affect the module's scorecard; the results are still good.

Theme Before After
Presentation & Onboarding 17.5 / 25 17.5 / 25
Integration 12.5 / 25 12.5 / 25
Credential Hygiene 18 / 20 18 / 20
Restricted-Environment 7.5 / 20 7.5 / 20
Engineering Quality 8 / 10 8 / 10
Overall 64 / 100 64 / 100
Full scorecard for this PR
Presentation & Onboarding Agent Integration Credential Hygiene Restricted-Environment Readiness Engineering Quality Overall
17.5 / 25 12.5 / 25 18 / 20 7.5 / 20 8 / 10 64 / 100
Drilldown

Presentation & Onboarding — 17.5 / 25

Criterion Max Score Notes
Configuration-mode examples 12 12 README provides documented examples for multiple major modes: standalone with API key, AI Gateway, Bedrock, Vertex AI, custom gateway, OAuth token, api_key_helper. Each has sensible defaults and clear configuration.
Coder-context framing 8 5.5 README names both Coder and Claude Code, explains authentication flows (AI Gateway, session tokens), and shows Coder-specific integration (coder_app, coder_env). However, lacks explicit explanation of what the module adds on top of Coder or where Coder fits in the broader Claude Code workflow.
Visual preview 5 0 No image, GIF, or video in README. Only icon reference.

Agent Integration — 12.5 / 25

Criterion Max Score Notes
AI governance 10 5 AI Gateway support is documented with enable_ai_gateway variable and examples showing authentication via session token. Agent Firewall support was explicitly dropped in v5 per the WARNING block ("v5 is a major refactor that drops support for...Boundary"). Only AI Gateway documented = half credit.
Dashboard entry point 5 5 coder_app example provided in "Standalone mode with a launcher app" section showing proper command execution with open_in = "slim-window".
Session continuity 5 0 No documentation of resuming existing sessions, session IDs, or persistent session managers (tmux, screen, boo).
Managed configuration 5 2.5 managed_settings variable documented with example showing permissions policy and reference to Claude Code settings schema. However, MCP configuration (mcp, mcp_config_remote_path) is documented but described as "user scope" rather than managed/enforced. Partial support for managed config.

Credential Hygiene — 18 / 20

Criterion Max Score Notes
Secrets marked sensitive 16 14 anthropic_api_key and claude_code_oauth_token variables marked sensitive = true. However, README examples show inline placeholder secrets (anthropic_api_key = "xxxx-xxxxx-xxxx") which caps this at less than full.
Non-hardcoded auth path 4 4 Multiple non-hardcoded paths documented: AI Gateway (enable_ai_gateway), api_key_helper for Vault/Secrets Manager, Bedrock with IAM chain, Vertex with ADC, OAuth token generation. Strong credential hygiene options.

Restricted-Environment Readiness — 7.5 / 20

Criterion Max Score Notes
Mirrorable artifact source 10 0 No module input variable overrides the Claude Code download URL. The install script uses hardcoded "curl -fsSL claude.ai/install.sh". claude_code_version pins the version but does not change the download source.
Bring-your-own binary 5 5 install_claude_code = false documented in "Advanced Configuration" example with claude_binary_path to point at pre-installed binary. Clear disable path.
Egress transparency 3 1.5 No dedicated README section for network/air-gapped environments. Endpoints scattered across examples (claude.ai/install.sh, Anthropic API, Bedrock, Vertex, AI Gateway, MCP remote URLs) but not enumerated in one place. At most half.
Runs without sudo 2 1 install.sh.tftpl uses sudo conditionally for managed-settings.d writes (lines with "if command_exists sudo; then sudo mkdir" and "sudo tee"). Core functionality (CLI install, user config) works without sudo, but managed_settings feature requires sudo. Sudo for optional feature with fallback = half.

Engineering Quality — 8 / 10

Criterion Max Score Notes
Input quality 6 6 Variables have clear descriptions, sensible defaults (claude_code_version = "latest", install_claude_code = true, telemetry.enabled = false). Comprehensive validation blocks for mutual exclusivity (enable_ai_gateway vs anthropic_api_key, use_bedrock vs use_vertex, api_key_helper conflicts).
Test coverage 4 2 main.test.ts provides end-to-end TypeScript tests covering install, auth modes, MCP, managed settings, telemetry, Bedrock/Vertex. main.tftest.hcl covers Terraform plan validation for variables and env resources. However, .tftest.hcl tests are primarily input validation rather than business logic (no apply tests, no script execution verification in HCL). Partial coverage.

Overall — 64 / 100


Scored against SCORECARD.md with claude-sonnet-4-5. Language-model scores are advisory.

…eprecated

Drop the link to the deleted Coder Tasks docs page and warn that the wiring
only applies to Coder versions before v2.36. The module still exposes
task_app_id and report_tasks, so the example stays for those deployments.
@david-fraley
david-fraley marked this pull request as ready for review August 18, 2026 14:22

> [!WARNING]
> If upgrading from v4.x.x of this module: v5 is a major refactor that drops support for [Coder Tasks](https://coder.com/docs/ai-coder/tasks) and [Boundary](https://coder.com/docs/ai-coder/agent-firewall). Keep using v4.x.x if you depend on them. See the [PR description](https://github.com/coder/registry/pull/879) for a full migration guide.
> If upgrading from v4.x.x of this module: v5 is a major refactor that drops support for Coder Tasks and [Boundary](https://coder.com/docs/ai-coder/agent-firewall). Keep using v4.x.x if you depend on them. See the [PR description](https://github.com/coder/registry/pull/879) for a full migration guide.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also mention Coder version 2.34 here maybe.

Comment on lines 89 to 94
### Coder Tasks Integration

To enable integration with [Coder Tasks](https://coder.com/docs/ai-coder/tasks), you need to define the `coder_task` data source, create the `coder_ai_task` resource, and configure the module with the task prompt.
To enable integration with Coder Tasks, you need to define the `coder_task` data source, create the `coder_ai_task` resource, and configure the module with the task prompt.

```tf
data "coder_task" "me" {}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete this whole section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants