How to Edit Agents in Eve

Last updated: September 30, 2026

Overview

An agent's configuration can be changed at any time from the agent editor: its name, description, tag, visibility, and the instructions or examples it runs on.

Editing is how an agent grows alongside your firm and improves in accuracy. Instructions written before the agent had ever run on a real matter can always be updated once you've seen a few real results, and tightening them after a few runs is a normal path rather than a sign something went wrong.

Before You Start

  • The agent already exists in your agents library.

  • Permission to edit it. You can edit any agent you created, and Firm Admins can edit any agent in the firm.

Open the Agent Editor

  1. Click Agents in the left navigation. The library shows your own agents plus anything shared across the firm.

  2. Find the agent. Use the search field, or narrow with the filter dropdown by tag, type or sharing setting. Filtering by tag is faster than scrolling once the library is large.

  3. Click the ••• menu on the right of the agent card.

  4. Select Edit. The editor opens with the current configuration loaded. Nothing changes until you save.

What You Can Change

Each field can be changed on its own. You do not have to touch one to save another.

Setting

What it controls

Worth knowing

Name

How the agent appears in the library and when it is run.

Name it for the job it does rather than the matter it came from. "Deposition Summary, Chronological" beats "Smith Agent v2".

Description

The explanatory text on the agent card.

This is what colleagues read when deciding whether to use it. Say what it produces and which documents to select before running.

Tag

Filtering and discoverability.

An agent carries one tag, so editing it replaces what was there. See 📄 How to Organize Agents with Tags in Eve.

Visibility

Only me or Shared across the firm.

Switching to Shared changes who depends on the agent's behavior, so test before you flip it.

Editing by Agent Type

  • Chat agents. Edit the prompt instructions. Specific beats general: "identify each injury with a supporting quote from the medical records, ordered by date of treatment" produces more consistent output than "summarize the injuries". When an agent keeps making the same mistake, add an explicit instruction ruling it out rather than rewriting the whole prompt.

  • Drafting agents. Add example DOCX files, or remove ones that are not helping. Examples move the output further than description does. If the output has drifted toward a style you do not want, look at whether one of the examples is pulling it there.

  • Communication agents. Edit the instructions that shape client-facing correspondence. Audience and tone are the levers, and both need stating explicitly: a status update to a commercial client and one to an individual plaintiff need different registers, and an agent will not infer that. Name the recipient type, the reading level, and anything the agent must never do, such as committing to timing, speculating on case value, or using legal terminology without explaining it. Firm standard language for common situations belongs in the instructions so every communication carries it.

  • Advanced configuration. Add background knowledge the agent should reference on every run, such as statutes, firm standards, definitions or jurisdiction requirements, so that context does not have to be supplied each time. Triggers, which run the agent automatically when conditions are met, are also set here.

Click Save. The updated agent is available immediately in the Agents tab and in any matter that can use it.

Test the Change

Run the edited agent on a matter where you already know what good output looks like, and compare. An edit that reads well in the editor does not always behave as expected. Two or three rounds of edit and test is normal.

Editing a Shared Agent

Colleagues are relying on the current behavior of a shared agent, and Eve does not support duplicating an agent, so there is no copy to experiment on. Editing the live agent is the only path. Test before saving, and tell people when the change is substantial.

When what you want is a variant rather than a replacement, build it as a new agent and leave the shared one alone.