You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ai-coder/agent-boundary.md
+7-29Lines changed: 7 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Agent Boundaries are process-level firewalls that restrict and audit what autonomous programs, such as AI agents, can access and use.
4
4
5
-
Example of Agent Boundaries blocking a process.
5
+
Example of Agent Boundaries blocking a process.
6
6
7
7
The easiest way to use Agent Boundaries is through existing Coder modules, such as the[Claude Code module](https://registry.coder.com/modules/coder/claude-code). It can also be ran directly in the terminal by installing the[CLI](https://github.com/coder/boundary).
8
8
@@ -11,7 +11,7 @@ The easiest way to use Agent Boundaries is through existing Coder modules, such
11
11
12
12
##Supported Agents
13
13
14
-
CoderBoundary supports the securing of any terminal-based agent, including your own custom agents.
14
+
Boundary supports the securing of any terminal-based agent, including your own custom agents.
15
15
16
16
##Features
17
17
@@ -21,24 +21,15 @@ Boundaries extend Coder's trusted workspaces with a defense-in-depth model that
21
21
-_Network policy enforcement_: block domains, subnets, or HTTP verbs to prevent exfiltration
22
22
-_Audit-ready_: centralize logs, exportable for compliance, with full visibility into agent actions
23
23
24
-
25
-
26
24
##Getting Started with Boundary
27
25
28
26
For Early Access, users can use Agent Boundaries through its[open source CLI](https://github.com/coder/boundary), which can be run to wrap any process or invoked through rules in a YAML file.
29
27
30
-
Eventually, users of Coder Premium can enable Agent Boundaries simply by updating to the latest versions of their preferred coding agent modules, which integrate with Coder with just a few lines of Terraform. Once configured by platform admins, developers get agent-ready environments automatically - no extra setup required.
31
-
32
-
33
28
34
-
35
-
###Option 2) Wrap the agent process with the Boundary CLI
29
+
###Wrap the agent process with the Boundary CLI
36
30
37
31
Users can also run Boundary directly in your workspace and configure it per template or per script. While free tier users won't get centralized policy management or the deeper, "strong isolation," they can still enforce per workspace network rules and log decisions locally.
38
32
39
-
There are two ways to integrate the open source Boundary CLI into a workspace.
40
-
41
-
####Wrap a command inline with flags
42
33
43
34
1. Install the[binary](https://github.com/coder/boundary) into the workspace image or at start-up. You can do so with the following command:
44
35
@@ -57,6 +48,10 @@ There are two ways to integrate the open source Boundary CLI into a workspace.
57
48
make fmt # Format code
58
49
make lint # Lint code
59
50
```
51
+
52
+
From here, there are two ways to integrate the open source Boundary CLI into a workspace.
53
+
54
+
#### Wrap a command inline with flags
60
55
1. Wrap the tool you want to guard. Below are some examples of usage:
61
56
62
57
```hcl
@@ -78,23 +73,6 @@ There are two ways to integrate the open source Boundary CLI into a workspace.
78
73
#### Use a config file (YAML) to set rules
79
74
80
75
Another option is to define rules in a YAML file, which only needs to be invoked once as opposed to through flags with each command.
81
-
82
-
1. Similarly to the previous method, install the [binary](https://github.com/coder/boundary) into the workspace image or at start-up. You can do so with the following command:
1. Use the included `Makefile` to build your project. Here are a few example commands:
88
-
89
-
```hcl
90
-
make build # Build for current platform
91
-
make build-all # Build for all platforms
92
-
make test # Run tests
93
-
make test-coverage # Run tests with coverage
94
-
make clean # Clean build artifacts
95
-
make fmt # Format code
96
-
make lint # Lint code
97
-
```
98
76
1. Create a YAML file to store rules that will be applied to all `boundary` commands run in the Workspace. In this example, we call it `boundary.yaml`.