Agents
Legible agents are AI coding assistants that run inside sandboxed containers with pre-configured access to your data through the semantic layer. Each agent gets its own isolated environment with credentials, network policies, and MCP connectivity — so it can query your data without direct database access.
How It Works
┌───────────────┐ ┌──────────────────────────────────┐
│ legible CLI │────▶| OpenShell Gateway (per org) │
└───────────────┘ │ ┌────────┐ ┌────────┐ ┌──────┐ │
│ │Agent A │ │Agent B │ │ ... │ │
│ │(Claude)│ │(Codex) │ │ │ │
│ └───┬────┘ └───┬────┘ └──────┘ │
└──────┼──────────┼────────────────┘
│ │
┌──────▼──────────▼───────────────────┐
│ Legible MCP Server │
│ (Semantic Layer + Query Engine) │
└─────────────────────────────────────┘
- You create an agent with
legible agent create - The CLI provisions a sandbox via OpenShell — an NVIDIA container-isolation runtime
- The sandbox connects to your Legible project through the MCP server
- All sandboxes in an organization share a single gateway that manages resources
Agent Types
Legible supports several AI agent runtimes:
| Type | Description |
|---|---|
claude | Anthropic Claude Code (default) |
codex | OpenAI Codex CLI |
opencode | Open-source OpenCode agent |
copilot | GitHub Copilot agent |
Quick Start
Prerequisites
- Legible CLI — Install the CLI
- OpenShell — Container isolation runtime (see OpenShell setup)
- Docker — Required by OpenShell for running sandboxes
- A Legible project with at least one connected data source
Create Your First Agent
# Log in and select a project
legible login
legible project use 1
# Create a Claude agent
legible agent create my-analyst
# Or create from a blueprint with a specific inference profile
legible agent create my-analyst --blueprint legible-default --profile anthropic
The CLI will:
- Ensure an org-scoped gateway exists (creates one if needed)
- Set up a credentials provider with your Legible API key
- Create an isolated sandbox container
- Apply a network policy restricting traffic to Legible endpoints
Interact with the Agent
# Open a shell inside the agent's sandbox
legible agent connect my-analyst
# View agent logs
legible agent logs my-analyst --tail
# List all running agents
legible agent list
Stop an Agent
legible agent stop my-analyst
Resource Limits
Each agent sandbox runs with configurable resource limits:
legible agent create my-analyst --cpus 8.0 --memory 32g
When using a blueprint, resource limits are defined in the blueprint spec and applied automatically.
| Resource | Default | Flag |
|---|---|---|
| CPU cores | 4.0 | --cpus |
| Memory | 16g | --memory |
Sandbox Naming
Sandboxes are namespaced by organization to prevent collisions across teams:
{org-slug}-{agent-name}
For example, if your org slug is acme and you create an agent called analyst, the sandbox name is acme-analyst.
What's Next
- OpenShell — Install and configure the container runtime
- Blueprints — Pre-configured agent templates for different data sources
- Gateways — Org-scoped gateway management and resource allocation