> ## Documentation Index
> Fetch the complete documentation index at: https://docs.machina.gg/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Agents

> The real fields on an Agent, and which ones are Studio-only today.

Every configuration change to an agent today happens **in Studio** — the CLI can run an agent and read its state ([`machina agent get`](/cli/commands/agent), [`machina agent run`](/cli/commands/agent)), but it has no `update`, `set-frequency`, or similar write command.

## Fields you can edit

| Field       | Where                               | Notes                                                                                                                                                             |
| ----------- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Title       | Agent → Edit                        | Free text.                                                                                                                                                        |
| Description | Agent → Edit                        | Free text.                                                                                                                                                        |
| Status      | Agent → Edit                        | `active` / `inactive`.                                                                                                                                            |
| Name        | —                                   | **Locked after creation.** Not editable from the form.                                                                                                            |
| Frequency   | Agent detail page, dedicated dialog | Minutes, stored as `context["config-frequency"]` (e.g. `0.5` = every 30 seconds). Editable inline both from the agents list and from the agent's own detail page. |

## Frequency in practice

Frequency is not part of the create/edit form above — it has its own small dialog on the agent's detail page (and an inline editor on the list view). Examples of what a value means:

| `config-frequency` | Runs              |
| ------------------ | ----------------- |
| `0.03`             | \~every 2 seconds |
| `0.5`              | every 30 seconds  |
| `1`                | every minute      |
| `60`               | every hour        |
| `1440`             | once a day        |

<Warning>
  There's no CLI equivalent for this today. If you're scripting agent setup, frequency has to be set through Studio (or through whatever mechanism the installed skill/template used to provision the agent in the first place — see [Creating Agents](/agents/creating-agents)).
</Warning>

## Workflows and documents

The agent's detail page shows the workflows it triggers and any documents associated with it — but that **Workflows tab is read-only** (`agents/[agent_id]/workflows/page.tsx` just renders `agents.view.data.workflows`, no add/attach action). Checked the two other places this could plausibly live:

* **"View Code"** on the agent detail page — a read-only JSON inspector (`react-inspector`'s `ObjectInspector`), not an editor.
* **The workflow's own create/edit form** — no agent-picker field either.

None of the three expose a way to attach a workflow to an agent from the Studio UI. Also checked every internal handoff doc in `machina-studio/docs/` — `ONBOARDING_BACKEND_REQUIREMENTS.md` confirms templates are "presets de agents/connectors/workflows" provisioned together at install time (matching [Creating Agents](/agents/creating-agents)), but nothing in that folder documents attaching a workflow onto an **already-existing** agent afterward.

So this isn't an unchecked gap — it's checked in the UI code, the workflow's own form, and every internal doc that mentions agents, and the manual attach flow doesn't turn up anywhere. It most likely happens through a direct backend API call outside any UI this repo could find. **Needs-validation**: if you need to wire a workflow onto an existing agent today, ask a Studio owner rather than trust an invented set of steps here.

## Related

* [Creating Agents](/agents/creating-agents) — the initial four-field form.
* [Operating Agents](/agents/operating-agents) — running and inspecting once configured.