Agent Environment
When an agent connects, it reports its environment to Wrapd — OS, hostname, whether it’s running in Docker, available shell, and which commands are installed. This info appears in the dashboard and is used by AI generation to suggest only commands your agent can actually run.
What gets reported
Section titled “What gets reported”| Field | Example (Host) | Example (Docker) |
|---|---|---|
| OS | linux | linux |
| Hostname | my-server | 3f4a2b1c9d8e |
| Type | Host | Docker |
| Shell | /bin/bash | /bin/sh |
| Available commands | curl, docker, pg_dump, node, git… | curl, jq, python3… |
Host vs Docker agents
Section titled “Host vs Docker agents”Host (binary) — the agent runs directly on your machine. It has access to everything installed on the system: Docker CLI, databases, system tools, package managers, and any software you’ve set up.
Docker — the agent runs inside a container. It can only use commands installed in the Docker image. By default it does not have access to:
- The Docker CLI (can’t manage containers from inside a container)
- Host databases or services (unless ports are mapped)
- Host filesystem (unless volumes are mounted)
- System tools like
systemctl
Viewing environment in the dashboard
Section titled “Viewing environment in the dashboard”Go to Dashboard > Agents, click on an agent, and the sidebar shows the full environment details including a tag list of every detected command.
The table also shows a Docker or Host badge for each connected agent.
How AI generation uses environment
Section titled “How AI generation uses environment”When you use Generate with AI, Wrapd automatically includes your connected agent’s environment in the context. The AI will:
- Only suggest commands that are available on your agent
- Warn if a requested tool isn’t installed
- Adapt commands for the detected OS and shell
If no agent is connected, the AI falls back to generic Linux defaults.
Choosing the right install method
Section titled “Choosing the right install method”For most users, the binary (host) install is recommended — it gives the agent full access to your system’s tools and is the simplest setup.
Use Docker when you want isolation or need to run the agent in an environment different from your host (e.g., specific OS, pre-installed tools).
Probed commands
Section titled “Probed commands”The agent checks for these commands at startup:
curl, wget, git, docker, python3, python, node, pg_dump, psql, mysql, redis-cli, jq, systemctl, apt, yum, apk, npm, pip, cargo, go, java
Commands not in this list can still be used — the probe is for visibility and AI context, not enforcement.