Agent and App Rename System#

The rename system lets users rename agents, apps, and chat sessions from multiple surfaces in the Agenta UI. The feature was introduced in PR #5202 and a follow-up cache bug was fixed in PR #5330.

Architecture Overview#

The rename system is built around three layers:

1. EntityIdentity module — shared hook and UI primitives used by all rename surfaces
2. EditAppModal — the rename-and-details dialog triggered from table row menus
3. Surface integrations — playground header (inline), agents table, app-management table, app-overview page

All rename surfaces share a single API call path and cache invalidation strategy through the useRenameApp hook. 1

EntityIdentity Module#

Located at web/oss/src/components/EntityIdentity/, this module was added in PR #5202 and exports three items. 1

useRenameApp hook#

The central piece. It:

• Calls updateWorkflow(projectId, { id, name, description, flags: { is_application: true } }) to persist the rename
• Invalidates invalidateWorkflowsListCache(), mutate(), and invalidateAppManagementWorkflowQueries() after success
• Exposes isDuplicateName(name, selfId) — case-insensitive guard that checks against the full apps list

All rename surfaces call only renameApp({ id, name }) and optionally supply an onRenamed callback; cache invalidation is centralized in the hook. 1

AgentNameInline component#

Inline editor used in the playground header. 1

• Renders the agent name as plain text with a hover-revealed pencil icon
• Enter edit mode by clicking the pencil or double-clicking the name
• Commit with Enter or blur; cancel with Escape
• Shows inline error if the proposed name is a duplicate
• Calls renameApp(...) then fires onRenamed(newName) so the caller can update local display state immediately

fields.tsx — UI primitives#

Three small presentational components used inside EditAppModal: 1

• FieldLabel — caption above editable or read-only fields
• CopyRow — read-only value with a copy-to-clipboard icon (check mark on success)
• TypeBadge — pill displaying app type (Agent / Chat / Completion / Custom workflow)

EditAppModal#

Before PR #5202: EditAppModal.tsx was a lightweight modal accepting appDetails, validating the new name (no duplicates, only letters/numbers/underscore/dash), calling updateAppName(appId, newName), and refreshing via mutate().

After PR #5202 refactor: The modal grows into a rename-and-details view. 1

• Callers pass only { id, name, onRenamed } — detail fields auto-populate from workflowArtifactQueryAtomFamily(workflowId)
• Editable: name (with duplicate validation), description
• Read-only (with copy): version, created date, slug, workflow ID
• TypeBadge shows app kind in the modal header

The same modal instance is reused across all rename surfaces (home agents table, agents page, app-management, app-overview). 1

Rename Surfaces#

The playground header maintains a local displayAgentName state for instant UI feedback before the cache refresh completes. 1

Cache Invalidation Bug and Fix (PR #5330)#

Bug: After renaming from the app-overview page, the page title stayed stale — the backend updated correctly, but the overview kept showing the old workflow name. 2

Root cause: useRenameApp invalidated the app-list and artifact caches but not the separate ["workflows", "detail", projectId, workflowId] query key that the overview page reads from. 2

Fix (PR #5330): Two files changed: 2

1. useRenameApp.ts — now also calls invalidateWorkflowCache(id) after the rename
2. store.ts (agenta-entities package, workflow state) — invalidateWorkflowCache(workflowId) enhanced to read workflowProjectIdAtom from the store and add an exact-match invalidation for ["workflows", "detail", projectId, workflowId]

This ensures that any React Query subscriber on the detail view immediately sees the updated name without a manual reload.

Cache keys invalidated after rename#

Key Files#

Related PRs:

• PR #5202 — feat: Rename agents and chat sessions from the playground and tables
• PR #5330 — fix: Refresh workflow name after rename