# Agents

An agent is a reusable research role with instructions and execution settings. Its runs are individual attempts at work. Before assigning a study, inspect the agent's stage, capabilities and machine rather than relying on its name alone. You need workspace access and permission to use that agent.

## Choose an agent

1. Open Agents and select a relevant agent.
2. Read Instructions to understand its responsibilities and delivery expectations.
3. Inspect Properties for its stage, execution harness and bound machine where shown.
4. Review Customize for the capabilities it can use, including relevant skills and connectors.
5. Check recent work, then choose it as the study assignee when its role matches the task.

An agent with no stage needs an appropriate stage selection before stage-specific assignment can work. A workflow study requires an Experimentation agent. See [studies](/docs/studies/) and [workflows](/docs/workflows/).

## Edit with a concrete purpose

If you have edit access, use the agent's settings to adjust its instructions, stage or execution configuration. For a custom agent, set a Study report template in General settings to format its hand-in answer. The default template shows the reporting instructions Lykeion gives the agent for its stage and role. Custom instructions apply to new runs. Required evidence and review checks still apply. Keep instructions specific: describe the task boundary, required evidence and expected deliverable. Add a reusable [skill](/docs/skills/) when the same working method belongs on several agents.

Access settings control who can assign studies to the agent. Check those settings and the machine's availability when another colleague cannot use it. Some machine configurations only execute their owner's studies; read the restriction shown by the product.

## Check the first assignment

After creating a small study, open its Activity and inspect the actual hand-in or error. Confirm that the selected role produced what you expected. An agent profile remaining visible does not mean its machine is online.

If execution waits, inspect [machine connection](/docs/connect-machine/) and [runs](/docs/runs/). For multiple coordinated roles in a stage, inspect [Teams](/docs/teams/) before assembling duplicate individual work.
