Setup
The workspace has an S3 bucket at/data, a RAM folder at /scratch, and
the gh and slack CLIs. Their credentials come from AWS Secrets Manager,
1Password and the server’s environment, and the agent never sees them. The
analyst profile sets what the agent can see and run.
workspace.yaml
workspace.yaml
workspace.yaml
Load the workspace
Load the workspace
- Python
- TypeScript
File Visibility Control
paths.hide makes /data/secrets and every *.pem absent, and paths.show
brings back /data/secrets/README.md. A hidden file is not refused, it does
not exist, whichever way the agent looks for it.
Shell commands:
- Python
- TypeScript
- CLI
Commands Control
commands.allow lists the only commands the session runs, so everything an
analyst does not need, such as rm, sed or curl, is off. For a CLI the
list names single verbs, so slack reads messages and members but never posts,
edits or uploads, and gh lists and views pull requests but cannot merge one or
call gh api. The agent reads the shell’s own Permission denied and exit 126;
the reason reaches the host on the result’s decision, shown under each line:
Agent Profile
An agent profile is a named set of rules underprofiles:. A session takes a
profile when it is created, and every line, file call and CLI in that session
follows it, however the agent connects. A profile can only narrow the
workspace, never widen it, so one workspace can serve agents with different
reach. The analyst profile above:
cwdandenvstart the session in/datawithTEAMset.mountskeeps/dataread-only, though the workspace may write it.pathsandcommandsare the rules from the two sections above.
vars, network, processes, command_limits and
policy; see Session Profiles.
Connect to a profile session
With the workspace on a Mirage server assecured, the
agent reaches the same session over HTTP, MCP or SSH:
- HTTP
- MCP
- SSH
Create the session under the profile, then run lines in it:
policy denied: line for the agent. See
Access for every way in.
Learn more
- Session profiles: every profile key and how rules match.
- Service credentials: every source a pointer can read from.
- CLIs: the bundled CLIs and their settings.
- Policies: rules in code, for what a profile cannot express.