⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@bdougie
Copy link
Collaborator

@bdougie bdougie commented Jan 13, 2026

Description

Waiting on #9497

This PR adds documentation for running Continue agents locally, including:

  • Updated agents overview documentation
  • New guide for running agents locally
  • Updated docs.json configuration

AI Code Review

  • Team members only: AI review runs automatically when PR is opened or marked ready for review
  • Team members can also trigger a review by commenting @continue-review

Checklist

  • I've read the contributing guide
  • The relevant docs, if any, have been updated or created
  • The relevant tests, if any, have been updated or created

Screen recording or screenshot

[TODO: Add screen recording or screenshot if applicable - see this PR as a good example]

Tests

Documentation changes - no tests required.


Continue Tasks

Status Task Actions
▶️ Queued Update docs on PR View
▶️ Queued Optimize Website Performance View

Powered by Continue


Summary by cubic

Adds documentation for running Continue agents locally with version-controlled agent files and GitHub Actions integration. Updates the Agents overview and navigation to make local agents easy to find and use, and fixes broken links in the Agents pages.

  • New Features

    • New guide: “Run Agents Locally” with quick setup, agent file format, CLI usage, CI workflow, and security best practices.
    • Agents overview updated with a “Local Agents” tab and card linking to the guide.
    • Navigation updated (docs.json) to include the new guide under CLI Guides.
  • Bug Fixes

    • Fixed internal anchor path in Agents intro to point to /agents/overview#pre-configured-agents.
    • Updated Mission Control link in Agents overview to https://hub.continue.dev/agents.

Written for commit 9a701e2. Summary will update on new commits.

- Update agents overview documentation
- Add new guide for running agents locally
- Update docs.json configuration

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>
@continue
Copy link
Contributor

continue bot commented Jan 13, 2026

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

2 similar comments
@continue-staging
Copy link

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@continue-development-app
Copy link

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

bdougie and others added 2 commits January 13, 2026 11:39
Removed redundant text from title to potentially fix Mintlify build issue

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>
Fixed incorrect path from /hub/agents/overview to /agents/overview for the pre-configured-agents anchor link

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>
bdougie and others added 2 commits January 13, 2026 14:27
- Remove draft_pr.md (no longer needed)
- Add discussion_response.md

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>
@bdougie bdougie closed this Jan 14, 2026
@github-project-automation github-project-automation bot moved this from Todo to Done in Issues and PRs Jan 14, 2026
@github-actions github-actions bot locked and limited conversation to collaborators Jan 14, 2026
Use 4 backticks for outer code fence to prevent nested code blocks
from breaking MDX parser.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@bdougie bdougie reopened this Jan 14, 2026
@github-project-automation github-project-automation bot moved this from Done to In Progress in Issues and PRs Jan 14, 2026
Replace inline workflow with Continue's reusable workflow which handles
agent discovery, parallel execution, and check reporting. GH_TOKEN is
now automatically provided for agents using the gh CLI.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@bdougie
Copy link
Collaborator Author

bdougie commented Jan 14, 2026

Waiting on #9497

@bdougie bdougie marked this pull request as ready for review January 14, 2026 01:09
@bdougie bdougie requested a review from a team as a code owner January 14, 2026 01:09
@bdougie bdougie requested review from RomneyDa and removed request for a team January 14, 2026 01:09
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jan 14, 2026
</Card>

<Card title="Use Descriptive Names" icon="tag">
Name agent files clearly: `conventional-title.md`, `security-scan.md`, `deploy-checklist.md`.
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 not certain but I think name: in the agent file will take precedence and is potentially preferred. Maybe worth noting they can both be used (I think)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Updated - clarified name field is displayed, filenames for organization

- Simplify the prompt and add more specific instructions
- Check if the agent has access to required tools
- Enable verbose logging: `cn --verbose --agent .continue/agents/my-agent.md`
- Review logs at `~/.continue/logs/cn.log`
Copy link
Collaborator

Choose a reason for hiding this comment

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

(debateably) mac-only file path

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Made platform-agnostic

<Card title="What You'll Build" icon="folder-open">
A local agent system that:
- Keeps agent definitions version-controlled alongside your code
- Runs agents with Continue CLI for local development
Copy link
Collaborator

Choose a reason for hiding this comment

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

potential confusion, the user would run the agent locally not the system

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed section

- Keeps agent definitions version-controlled alongside your code
- Runs agents with Continue CLI for local development
- Automates agent execution on pull requests via GitHub Actions
- Applies consistent workflows across your team
Copy link
Collaborator

Choose a reason for hiding this comment

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

this bullet point feels unnecessary

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed section

- Applies consistent workflows across your team
</Card>

## Why Local Agents?
Copy link
Collaborator

Choose a reason for hiding this comment

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

Potential confusion: "Local agents"; it's in github and that's where the value is. Maybe "codebase" agents or similar?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The alternative is Cloud agents. Using the word local is to distinguish between what's in mission control

Copy link
Collaborator

Choose a reason for hiding this comment

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

The distinction makes sense, I think the word "local" might be a point of confusion

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Added clarifying note at top distinguishing local (repo) vs cloud (Mission Control)

--agent .continue/agents/analysis-only.md

# Always ask before running commands
cn --ask "Bash(*)" --agent .continue/agents/my-agent.md
Copy link
Collaborator

Choose a reason for hiding this comment

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

--ask will not work in CI/CD since user can't intervene, so maybe best if we don't mention it

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed

Before enabling fully automated agents:

1. **Test locally first** - Run agents with `cn` to verify behavior
2. **Use `--ask` mode** - Require approval for sensitive operations during testing
Copy link
Collaborator

Choose a reason for hiding this comment

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

see above

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed


1. **Test locally first** - Run agents with `cn` to verify behavior
2. **Use `--ask` mode** - Require approval for sensitive operations during testing
3. **Review CI logs** - Check what commands agents execute in your workflows
Copy link
Collaborator

Choose a reason for hiding this comment

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

unclear if the commands the agents execute will show up in logs like this


Continue provides a [reusable workflow](https://github.com/continuedev/continue/blob/main/.github/workflows/continue-agents.yml) that handles agent discovery, parallel execution, and GitHub Check reporting.

### Using the Reusable Workflow (Recommended)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Says "Recommended" but it's the only proceeding option

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed label

```bash
# Use your GitHub CLI token
export GH_TOKEN=$(gh auth token)
cn --agent .continue/agents/my-agent.md
Copy link
Collaborator

Choose a reason for hiding this comment

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

must set ANTHROPIC_API_KEY locally as well

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Added to Environment Variables section

sestinj
sestinj previously approved these changes Jan 15, 2026
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jan 15, 2026
- Add clarifying note distinguishing local vs cloud agents
- Remove redundant CardGroup section
- Fix API key naming to ANTHROPIC_API_KEY
- Clarify GitHub CLI pre-installed on runners
- Remove unnecessary tools: built_in from examples
- Rename "Rules" to "Guidelines" to avoid frontmatter confusion
- Flip headless/TUI order (headless is typical)
- Simplify frontmatter table, link to reference
- Move GitHub Actions section before Security
- Remove --ask from CI guidance (requires user intervention)
- Fix mac-only log path
- Add ANTHROPIC_API_KEY to local env vars section
- Clarify name field vs filename in best practices

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@bdougie bdougie changed the title Add documentation for running agents locally docs: Add documentation for running agents locally Jan 15, 2026
@sestinj sestinj merged commit 17740ec into main Jan 15, 2026
56 of 60 checks passed
@sestinj sestinj deleted the bdougie/run-agents-docs branch January 15, 2026 18:37
@github-project-automation github-project-automation bot moved this from In Progress to Done in Issues and PRs Jan 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants