Skip to content

Conversation

@bpmct
Copy link
Member

@bpmct bpmct commented Dec 10, 2025

Updates Tasks documentation to emphasize its API-first design for automation workflows like GitHub Actions, CI/CD pipelines, and scheduled jobs. Adds common use case examples and clarifies that tasks can be triggered via API, CLI, or web UI.

🤖 Generated with Claude Code

Updates Tasks documentation to emphasize its API-first design for
automation workflows like GitHub Actions, CI/CD pipelines, and scheduled
jobs. Adds common use case examples and clarifies that tasks can be
triggered via API, CLI, or web UI.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@david-fraley david-fraley added the doc-check Assign this label to PRs to check for any doc changes. label Dec 11, 2025
@github-actions
Copy link

Copy link
Collaborator

📚 Documentation Check

✨ No Changes Needed

This PR already contains comprehensive documentation updates to docs/ai-coder/tasks.md. The changes effectively:

  • Reposition Tasks as an "API-first system for automating software development workflows"
  • Add a new "Common Use Cases for Task Automation" section with concrete examples (CI/CD integration, issue triage, scheduled maintenance, code review assistance, documentation generation)
  • Expand the "Command Line Interface" section to "Command Line Interface and API Access" with detailed links to CLI docs, API reference, and GitHub Actions integration
  • Clarify that tasks can be triggered via API, CLI, or web UI
  • Link to the GitHub Actions integration guide

The documentation updates are well-aligned with the PR's goal of emphasizing Tasks' automation capabilities and are complete as-is.


This comment was generated by an AI Agent through Coder Tasks

Copy link
Collaborator

📚 Documentation Check

✅ Updates Needed

Based on the new "API-first automation system" positioning in this PR, the following files need updates to maintain consistency:

  • docs/ai-coder/index.md - Lines 13-15 describe Tasks as "an interface inside Coder to run and manage coding agents with a chat-based UI." This misses the API-first automation emphasis and should be updated to highlight that Tasks is designed for CI/CD pipelines, GitHub Actions, scheduled jobs, and can be triggered via API, CLI, or web UI.

  • docs/ai-coder/tasks-core-principles.md - Line 5 has a generic description "Coder Tasks is Coder's platform for managing coding agents" that should be updated to emphasize the API-first automation system positioning and integration with CI/CD and issue tracking workflows.

  • docs/tutorials/quickstart.md - Lines 241-242 describe Tasks as "an interface that allows you to run and manage coding agents" which should be updated to align with the new positioning that emphasizes automation workflows and programmatic access.

📝 Rationale

This PR repositions Tasks from a simple "interface for running agents" to an "API-first system for automating software development workflows." The three files above still use the old positioning language, creating inconsistency in how users understand what Tasks is designed for.

The updated language in tasks.md emphasizes:

  • Automation scenarios: CI/CD, GitHub Actions, scheduled jobs, issue triaging
  • Programmatic access: API, CLI, and web UI
  • Autonomous workflows: Agents working independently on well-defined tasks

These three files should reflect the same positioning for consistency across the documentation.


This comment was generated by an AI Agent through Coder Tasks

Copy link
Collaborator

@david-fraley david-fraley left a comment

Choose a reason for hiding this comment

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

Left some thoughts. Also ran the doc-check workflow on the PR; let's address those comments as well

# Coder Tasks

Coder Tasks is an interface for running & managing coding agents such as Claude Code and Aider, powered by Coder workspaces.
Coder Tasks is an API-first system for automating software development workflows with any AI coding agent, like Claude Code and Sourcegraph Amp. Tasks are designed for automation scenarios like CI/CD pipelines, GitHub Actions, scheduled jobs, and issue triaging where agents can work autonomously on well-defined tasks.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Coder Tasks is an API-first system for automating software development workflows with any AI coding agent, like Claude Code and Sourcegraph Amp. Tasks are designed for automation scenarios like CI/CD pipelines, GitHub Actions, scheduled jobs, and issue triaging where agents can work autonomously on well-defined tasks.
Coder Tasks is an API-first system for automating software development workflows with any AI coding agent, like Claude Code and Sourcegraph Amp. Tasks are meant for augmenting and automating repeatable parts of your SDLC with AI and coding agents. They can easily be integrated into your work management systems like GitHub or project trackers like Jira.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm unsure I like the Jira callout here, but it's kinda on the roadmap


Tasks are designed for automation workflows where AI agents can work independently:

- **CI/CD Integration**: Trigger tasks from GitHub Actions, GitLab CI, or Jenkins to automatically address issues, update dependencies, or generate documentation when code changes
Copy link
Collaborator

Choose a reason for hiding this comment

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

This item feels out of place. It's not a use case, but rather where it can be integrated. I recommend removing


- **CLI Commands**: See [Tasks CLI](./cli.md) for creating, monitoring, and managing tasks from scripts or CI/CD pipelines
- **REST API**: See [Tasks API Reference](../reference/api/tasks.md) for HTTP endpoints to integrate task creation into your automation workflows
- **GitHub Actions**: Use the [create-task-action](https://github.com/coder/create-task-action) to trigger tasks from GitHub workflows
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would remove this as it feels like a random inclusion to the list. If we want to keep the callout, we can add a new section around "current and planned integrations"

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

Labels

doc-check Assign this label to PRs to check for any doc changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants