2025-04-01 19:57:05 -05:00
|
|
|
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
|
|
|
|
|
|
2026-02-02 07:48:34 -06:00
|
|
|
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.
|
2025-04-01 19:57:05 -05:00
|
|
|
|
|
|
|
|
## 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.
|
2026-02-02 07:48:34 -06:00
|
|
|
This will likely involve editing your template for Agents to set different
|
|
|
|
|
scopes or tokens from the standard one.
|
2025-04-01 19:57:05 -05:00
|
|
|
|
|
|
|
|
Additional guidance and tooling is coming in future releases of Coder.
|
|
|
|
|
|
2025-10-08 09:14:14 -07:00
|
|
|
## Set Up Agent Boundaries
|
2025-04-01 19:57:05 -05:00
|
|
|
|
2026-02-02 07:48:34 -06:00
|
|
|
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).
|