Skip to main content

Agents

Create a worker​

Open Agents, choose the create-agent action and set:

  • A unique name and a focused system prompt describing the work.
  • An existing absolute working directory on the daemon's machine.
  • A project, if this agent belongs to one.
  • A backend and model from the available catalogue.
  • The permission mode, skills and MCP servers needed for the task.

Save, open the agent's chat and start with a small request. An agent configuration is reusable; creating it does not itself complete a mission.

For the CLI equivalent, prepare a plain-text prompt file and replace the example path with your project:

timon agent create project.writer --cwd /path/to/project --prompt-file writer.md
timon list
timon spawn project.writer "Summarize the README in this project."

Customize a role prompt​

In the agent editor, open Manage roles and select a built-in role. Edit its instructions and save. The role is marked Modified; its identity, icon, colour, model and permission defaults remain unchanged.

The saved prompt applies to all agents using that role in new missions. Choose Reset prompt to discard the customization and restore the prompt shipped with Timon. Roles without a customization follow prompt updates in future releases. Built-in roles cannot be deleted.

Skills and tools​

Skills are SKILL.md instruction packages attached to an agent. MCP servers expose tools. Attach the ones the agent actually needs; a backend's hosted account connectors and Timon's configured MCP servers are different sources of tools.

Permission behaviour depends on the backend's capabilities. Some support interactive tool approval; others receive a sandbox policy fixed when the mission starts. Read the editor's explanation for the selected backend instead of assuming every model can show the same permission dialog.

Use Projects to share role defaults across a project and Missions to follow the worker's output.

Create a skill​

Open Skills, choose New TIMON skill, enter an ID and write the instructions in SKILL.md content, then save. IDs use lowercase letters, digits, dots, underscores and hyphens; . and .. alone are not valid IDs. The form shows missing instructions and invalid IDs before sending a request. If saving fails, your draft stays open so you can correct it or retry.