Skip to content

feat: update tasks docs #18659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 24 commits into from
Jul 7, 2025
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix more broken links
  • Loading branch information
bpmct committed Jul 4, 2025
commit 02e6b9c4790d258951c50e2ce62464be46db17a2
2 changes: 1 addition & 1 deletion docs/ai-coder/best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Below are common scenarios where AI coding agents provide the most impact, along
| Scenario | Description | Examples | Tools |
|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
| **Automating actions in the IDE** | Supplement tedious development with agents | Small refactors, generating unit tests, writing inline documentation, code search and navigation | [IDE Agents](./ide-agents.md) in Workspaces |
| **Developer-led investigation and setup** | Developers delegate research and initial implementation to AI, then take over in their preferred IDE to complete the work | Bug triage and analysis, exploring technical approaches, understanding legacy code, creating starter implementations | [Tasks](./tasks.md), to a full IDE with [Workspaces](./workspaces.md) |
| **Developer-led investigation and setup** | Developers delegate research and initial implementation to AI, then take over in their preferred IDE to complete the work | Bug triage and analysis, exploring technical approaches, understanding legacy code, creating starter implementations | [Tasks](./tasks.md), to a full IDE with [Workspaces](../user-guides/workspace-access/index.md) |
| **Prototyping & Business Applications** | User-friendly interface for engineers and non-technical users to build and prototype within new or existing codebases | Creating dashboards, building simple web apps, data analysis workflows, proof-of-concept development | [Tasks](./tasks.md) |
| **Full background jobs & long-running agents** | Agents that run independently without user interaction for extended periods of time | Automated code reviews, scheduled data processing, continuous integration tasks, monitoring and alerting | [Tasks](./tasks.md) API *(in development)* |

Expand Down
2 changes: 1 addition & 1 deletion docs/ai-coder/custom-agents.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Custom agents beyond the ones listed in the [Coder registry](https://registry.co
## Prerequisites

- A Coder deployment with v2.21 or later
- A [Coder workspace / template](./create-template.md)
- A [Coder workspace / template](../admin/templates/creating-templates.md)
- A custom agent that supports Model Context Protocol (MCP)

## Getting Started
Expand Down
2 changes: 1 addition & 1 deletion docs/ai-coder/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ environments.

## Use Trusted Models

Most [agents](./agents.md) can be configured to either use a local LLM (e.g.
Most agents can be configured to either use a local LLM (e.g.
llama3), an agent proxy (e.g. OpenRouter), or a Cloud-Provided LLM (e.g. AWS
Bedrock). Research which models you are comfortable with and configure your
Coder templates to use those.
Expand Down
Loading