# Configure Your Agent

Agent settings are managed with `dvx agent config`. Configuration is layered - platform defaults, then organization defaults, then per-agent overrides - so a value you set on a specific agent wins over the org default.

See what's set on an agent:

```bash
dvx agent config list my-agent
```

## Set the model

Point an agent at a specific model:

```bash
dvx agent config set my-agent model --value claude-sonnet-4-6
```

To set a default for every agent in your organization instead, use org-level config:

```bash
dvx config set agent model --value claude-sonnet-4-6
```

## Set the system prompt

Give the agent standing instructions - its role, tone, and any domain context:

```bash
dvx agent config set my-agent system_prompt --value "You are a release assistant for the platform team. Be concise."
```

## Connect a Telegram channel

Let people talk to the agent over Telegram (see [Set Up an Agent](/agent-setup/) for the full walkthrough):

```bash
dvx agent channel telegram link my-agent \
  --bot-token '123456:ABC-DEF...' \
  --allowed-users 123456789,987654321
```

## Set the LLM API key

The key the agent uses to call its model is a **secret**, not config. Set it once at the org level and every agent inherits it:

```bash
dvx secret set llmproxy:llm.api_key --value sk-ant-...
```

See [Manage secrets](/cli-secrets/) for per-agent overrides.

## Remove a value

```bash
dvx agent config delete my-agent system_prompt
```

> Run `dvx agent config --help` to see the full set of available keys, and `dvx config list` to inspect organization and platform defaults.