Agentome GitHub
Contents

Agents

This page covers everything you do with an agent: create it, write its instructions, give it skills and tools, decide what it may do on its own, look after its memory, schedule its work, choose where it runs, hand it to someone else and keep its cost in check.

An agent can do any job: develop, test, analyse, write documentation, review contracts, manage a backlog. Its role comes from its instructions, its skills and its tools.

New to Agentome? Read Concepts first: it explains agents, projects, tasks and runs.

Your agents

Open Agents in the sidebar. The list shows the agents you own, with their Role title, Owner, Accepted and Cost per task over the last 30 days, and their Last run. While an agent is at work, Last run names its task; click it to open the run. Click a row to open the agent in the editor. The Archived tab, next to Active, lists archived agents.

The Agents page: Payments backend and Checkout QA with their role titles, owner Ann Admin, share of accepted work, cost per task and last run

Create an agent

You can start an agent from a role template, from a blank agent, or from a file. On Free, an installation can have up to five active agents; more need a license key.

From a role template

  1. Open Agents and click New agent.
  2. In the list, pick a role template, such as Backend developer, Frontend developer, QA engineer, Code reviewer, Technical writer, Release manager or Product owner. Pick Blank agent to start empty and write the instructions yourself.
  3. Check Name and Role title. A template fills both in; whatever you type stays when you pick another template.
  4. Click Create agent. The new agent opens in the editor.

A template is a starting point. It fills in the instructions, a preferred model and per-run limits; after that, the agent is yours to change, and a later change to the template does not change your agent. The agent sheet shows which template an agent came from under Template.

The New agent dialog: role templates with a line on each, Backend developer selected, and the Name and Role title fields

From a file (Import)

An agent file is an .agent.json file: one exported from Agentome, or one from the agent catalog at agentome.ai/agents.

  1. Open Agents and click Import.
  2. Click Choose a file and pick the .agent.json file.
  3. Check what the file brings: the agent's name and role, its Skills, its MCP servers and, for a catalog agent, where it comes from and under which license. If it is the wrong file, click Choose another file.
  4. Click Import agent.

The agent's skills join your library as your own skills. Where your library already has the same text, that skill is used as it is. The agent gets the MCP servers of your library that have the same names. If the file names servers your library does not have, the dialog lists them before the agent opens: add them in Library (see Integrations), then give them to the agent in its Tools & policies section.

An older agent file brings only the agent itself, and the dialog says so.

Duplicate and export

Both buttons are on the agent sheet, the panel on the right of the editor.

The agent editor

The editor is one page. On a wide screen it has three columns:

The agent editor for Payments backend: the sections on the left, its instructions in the middle, and its sheet on the right

Identity

The top of the page is the agent's name and role title. Click either to edit it. Under them are the projects the agent is on; an agent on no project reaches no repository. You add an agent to a project from the project's page; see Projects and tasks. When its owner has a computer connected, a chip says Runs on and names it.

The agent sheet

The sheet sums up the agent:

Preview workspace

Click Preview workspace on the sheet to see exactly what a run of the agent gets. The dialog has two tabs:

Click Copy to copy the file you are looking at, and Done to close.

Next to CLAUDE.md, a run also gets each skill's SKILL.md, the agent's memory documents as they were when the run started, and, for a task in a project, a PROJECT.md about the project. The preview shows the saved agent: if you have unsaved changes, it says so, and you see them only after you save.

Preview workspace: the CLAUDE.md of Payments backend, with its instructions and the list of its skills

Saving

The sections save in two ways.

If you try to leave the page with unsaved edits, Agentome asks Leave without saving?. Click Keep editing to stay, or Leave without saving to drop them. The browser also asks before you close or reload the tab.

Instructions

The instructions are the agent's job description: what it does, how it works, and when a task is done. Write them in Markdown. They go into the agent's CLAUDE.md as they are, under an Instructions heading.

Edit them on the Write tab and read them formatted on Preview. An agent with instructions opens on Preview, an empty one on Write.

Good instructions say what the agent owns and what it does not, the steps of a typical task, what it checks before it says it is done, and what it must never do. The role templates are a good model to start from.

Skills

A skill is a SKILL.md file that tells an agent how to do one kind of work, such as writing release notes or reviewing a migration. Skills live in the Library, and an agent reads one when a task calls for it.

To give the agent a skill, click Add a skill in the Skills section, search for the skill and pick it; the list shows each skill with its version. To take a skill away, click the cross on its chip.

Shared and private skills

In Library, skills come in three groups: Yours, Shared by others and From Agentome. A skill you add is private: only you can give it to your agents until an admin opens it and chooses Share with everyone. A private skill shows private on its chip in the editor, and the sheet counts private skills under Knows.

To add a skill to the library, open Library, click Add a skill, paste the SKILL.md, and click Add skill. Its frontmatter names the skill and says what it is for.

The Library: skills grouped as Yours, Shared by others and From Agentome, with a skill open on its SKILL.md, version and who it is shared with

Versions

Each skill has versions. To change one of your skills, open it in Library, click Edit, and click Save as a new version. Keep the name to save a new version; a new name makes a new skill.

An agent keeps the version it was given; only a skill From Agentome is updated in place when Agentome is. When the library has a newer version, the editor shows Move to version with its number next to the skill's chip. Click it when you are ready for the agent to use the new text. The skill's page in the library lists which of your agents have it, under Used by.

Team

The Team section says which team the agent leads and which teams it is a member of, each as a link to the team's page. If the agent leads no team, you can click Create a team it leads. You add members on the team's page. An agent on the Codex engine cannot lead a team. Teams, nested teams and how a lead splits a task are in Teams.

The Team section: Payments backend leads a team with Checkout QA as a member

Tools and policies

The Tools & policies section decides what the agent can reach and what it may do without asking.

MCP servers from the library

At the top of the section, click Add an MCP server and pick one of the servers in your library. Its tools join the list below under the server's name. To take a server away, click the cross on its chip. The server's secret stays on Agentome and never reaches the computer that runs the agent. You add servers to the library in Library with Add an MCP server; see Integrations.

Add an MCP server in the Library: its name, address, sign-in and what it does

Tools & policies: the MCP servers of Payments backend above the list of its tools

Policies

Each tool has one of three policies. Click one next to the tool to change it; it saves at once and applies to the next call.

The tools come in groups: the code host (create a branch, open a change request, read a change request and its pipeline failures, reply on it), the agent's task, its memory, the projects' knowledge, Jira, and each MCP server. The Workspace group is always allowed: those are the engine's own tools, such as reading and editing files in the run's workspace, which it uses with nobody to ask.

Until you change them, opening a change request and commenting on a Jira issue ask first, every tool of an MCP server asks first, a team lead's Start a team step asks first, and the rest are allowed.

The Auto and Manual switch above the list sets every tool at once: Auto allows them all, Manual makes them all ask. A tool you denied stays denied either way.

Policies of Payments backend: each tool with Allow, Ask or Deny; Open a change request set to Ask

What Ask does

When the agent calls a tool set to Ask, the call stops and waits in Approvals. The run shows as waiting for approval. The owner sees what the agent wants to do and the run so far, and clicks Approve or Deny; the run goes on with that answer. The time a run waits for a person does not count against its time limit.

Approvals on the web and on a phone are in Approvals and control.

Memory

An agent's memory is a set of Markdown documents that carry what it learned from one run to the next. There is MEMORY.md, and any number of documents in memory/, such as memory/stripe.md. Each run gets them beside its CLAUDE.md, as they were when the run started, and the agent saves a document again with its memory tool when it learns something worth keeping. The Memory section lists the documents with their current version and when they changed.

The Memory section: MEMORY.md and memory/stripe.md with their versions, and a document open on its history

Read and edit a document

  1. Click a document. It opens on Document, formatted.
  2. Click Edit, change the text, and click Save.

Every save makes a new version; the old one stays. If the agent or someone else changed the document after you opened it, Agentome refuses the save and says so. Your text stays in the field so you can copy it; close the document, open it again, and make your change on the new version.

Add a document

  1. Click Add a document.
  2. In Path, type MEMORY.md or a name in memory/, such as memory/release-steps.md.
  3. Write the text and click Save.

The agent reads it in every run, beside its instructions. Use this to give the agent a note it should keep in mind.

Versions and reverting

Open a document and click History. On the left are its versions; click one to see what changed from the version before it, line by line, and who wrote it: by a run, with a link to that run, or by a person's name.

To go back, pick an earlier version and click Revert to version with its number. Reverting saves that text as a new version, so nothing is lost and you can revert the revert.

Schedules

A schedule gives the agent the same task on set days at a set time, as if someone filed it.

Add a schedule

  1. In the Schedules section, click New schedule.
  2. Pick the Project its tasks are filed in. Every task belongs to a project, so the agent must be on at least one; if it is on none, the dialog says so and links to Projects.
  3. In Task, name the task, for example "Write the weekly release notes".
  4. In What to do, describe the work in Markdown. It goes to the agent as it is.
  5. Under Days, click the days it runs. Monday to Friday are on to start with.
  6. Pick a Time, in half hours, and a Time zone. The time zone starts as your browser's.
  7. Click Add schedule.

The list shows each schedule with when it runs, its time zone and when it last ran. Use the switch on a row to pause or resume it. To delete one, open its Actions menu and click Remove.

A scheduled task runs where the agent works (see Engine and model). On the owner's computer, the run waits until the owner is at the computer; on the server, it starts at once. If the agent has reached its monthly limit, the task is still made and waits for its owner. A minute missed while the Agentome server was down is skipped, not caught up.

Access, transfer and archive

Access

The Access section lists who holds the agent: its owner, and, while it is lent, who has it until which day. Only its owner can open and run an agent. To let someone else work with an agent, transfer it to them.

Transfer ownership

Transfer an agent when its owner goes on holiday, changes role or leaves. The agent's memory, history and settings go with it.

  1. Save any unsaved changes first; Transfer ownership stays unavailable until you do.
  2. On the agent sheet, click Transfer ownership.
  3. In New owner, choose a person.
  4. In Comes back, leave Never: it is theirs for good, or pick the day it returns to you.
  5. Click Transfer.

Transfer Payments backend: the new owner, and Comes back set to a date

From then on, its runs go to the new owner's computer and its approvals to them, and you no longer see it. With a return day, the agent comes back to you by itself on that day. Until then, the person who has it can only send it back early: Transfer ownership on their sheet offers Return now.

Keep in mind:

When a person leaves, an admin can hand every agent they own to someone else at once with Transfer agents in Admin → People; see Administration.

Archive

Click Archive on the agent sheet and confirm. The agent takes no more runs, its queued runs are cancelled, and it leaves the sidebar and the Active list. Its history stays. To bring it back, open it from the Archived tab and click Unarchive on its sheet.

Budget

The Budget section limits what one run, and a month of runs, may use. Save after editing.

Per-run limits

Minutes per run, Turns per run and Tokens per run: a run stops at the first limit it reaches. An empty field uses the platform default shown in it.

Monthly limit

Needs a license key.

Monthly limit, USD: when the agent's spend this month reaches it, no new run starts. Its owners hear of it at 80%. Leave it empty for no limit.

When a monthly limit is set, the section shows this month's spend against it. When the limit is reached, new runs are refused and a Continue this month button lets the agent go on until the month ends. To give it more room for good, raise the limit.

Project budgets and run limits across agents are in Approvals and control.

Engine and model

The Engine & model section decides what runs the agent, where, and on which model. Save after editing.

Engine

Changing the engine clears the model, since each engine has models of its own.

Where it works

On the server

Needs a license key.

By itself also needs a model connection. Until both are there, the option is unavailable, and the line under it says what is missing. An admin adds model connections in Admin → Models; see Administration.

Model

On the owner's computer, Model offers Default, which lets the engine choose, and the engine's models, such as Claude Opus 5.5 or Claude Sonnet 5.5 for Claude Code, and GPT-5 Codex or GPT-5 for Codex.

On the server, first pick a Model connection, then a Model from that connection. Claude Code runs Claude models only; Codex runs the rest.

An admin also sees Allow a shell on the server for a server agent. With a shell the agent could read the connection's key, so turn it on only for an agent that has to run commands, such as tests.

Quality

The Quality section shows how the agent's work landed over the last 30 days.

Needs a license key.

The Quality section of Payments backend: accepted share, first-go share, merged share, cost and time per task, and the tasks that came back most

Edit this page on GitHub