mirror of
https://github.com/coder/coder.git
synced 2026-06-03 13:08:25 +00:00
blinkagent[bot]
c75c57c250
## Summary This PR restructures the Agent Boundaries documentation to improve URL clarity and consistency: ### Changes - Renames `/docs/ai-coder/boundary/` to `/docs/ai-coder/agent-boundaries/` - Renames `agent-boundary.md` to `index.md` for cleaner URLs - Updates all internal doc references to the new paths - Updates `manifest.json` with new paths - Updates prose references from "Boundary" to "Agent Boundaries" throughout the documentation (33 changes across 4 files) ### New URL structure | Old URL | New URL | |---------|----------| | `/docs/ai-coder/boundary/agent-boundary` | `/docs/ai-coder/agent-boundaries` | | `/docs/ai-coder/boundary/nsjail` | `/docs/ai-coder/agent-boundaries/nsjail` | | `/docs/ai-coder/boundary/landjail` | `/docs/ai-coder/agent-boundaries/landjail` | | `/docs/ai-coder/boundary/rules-engine` | `/docs/ai-coder/agent-boundaries/rules-engine` | | `/docs/ai-coder/boundary/version` | `/docs/ai-coder/agent-boundaries/version` | ### Follow-up required Redirects need to be added to `coder/coder.com` for the old URLs: - `/docs/ai-coder/agent-boundary` → `/docs/ai-coder/agent-boundaries` (this one is currently 404'ing from Google search results) - `/docs/ai-coder/boundary/:path*` → `/docs/ai-coder/agent-boundaries/:path*` --- Created on behalf of @mattvollmer --------- Co-authored-by: blink-so[bot] <211532188+blink-so[bot]@users.noreply.github.com> Co-authored-by: Matt Vollmer <matthewjvollmer@outlook.com>
32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
As the AI landscape is evolving, we are working to ensure Coder remains a secure
|
|
platform for running AI agents just as it is for other cloud development
|
|
environments.
|
|
|
|
## Use Trusted Models
|
|
|
|
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.
|
|
|
|
## Set up Firewalls and Proxies
|
|
|
|
Many enterprises run Coder workspaces behind a firewall or a proxy to prevent
|
|
threats or bad actors. These same protections can be used to ensure AI agents do
|
|
not access or upload sensitive information.
|
|
|
|
## Separate API keys and scopes for agents
|
|
|
|
Many agents require API keys to access external services. It is recommended to
|
|
create a separate API key for your agent with the minimum permissions required.
|
|
This will likely involve editing your template for Agents to set different
|
|
scopes or tokens from the standard one.
|
|
|
|
Additional guidance and tooling is coming in future releases of Coder.
|
|
|
|
## Set Up Agent Boundaries
|
|
|
|
Agent Boundaries are process-level "agent firewalls" that lets you restrict and
|
|
audit what AI agents can access within Coder workspaces. To learn more about
|
|
this feature, see [Agent Boundaries](./agent-boundaries/index.md).
|