Repository navigation
Add agent nicknames to tell apart agents with the same name - #70
Merged
Merged
Conversation
Optional, unique (ignoring case) among enabled agents, set when connecting or later on the agent page, and shown instead of the card name across the console, inbox, approvals, notifications and audit trail. The agents list also shows each card's host and port. Schema version 9. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lu73uozkZGX8gP8LWNbBqt
The nickname leads; the name on the agent's card stays visible on the agents list and page, the chat header and picker, and in brackets in dropdowns. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lu73uozkZGX8gP8LWNbBqt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
Two registrations can advertise the same card name (for example the same agent built with LangGraph and with ADK), which makes them impossible to tell apart in lists, chat, the inbox and approvals. These two commits were pushed to
claude/id-labelsafter #67 had already merged, so they never reachedmain; this puts them in a PR of their own, unchanged (cherry-picked onto currentmain).Migration0009_AgentNicknameand schema version 9 (adds a nullablenicknamecolumn toagents).connect-an-agent.md,use-the-console.md,http-api.md) andCHANGELOG.mdare updated in the same commits, with tests:agent-label.test.ts,agent-nickname-card.test.tsx,agent-store.test.tsand additions to the agent-settings and database tests.Commits:
a15e406andf54f685fromclaude/id-labels, applied as7ff8ab9and3411020.How it was verified
Only
tsc --noEmitwas run on the cherry-picked branch, and it is clean. A dry-run merge of the original branch intomainhad no conflicts. Lint was started but I did not wait for it.Not verified, deliberately: I did not run the unit tests, the database and migration tests, the build or the HTTP scripts, and I did not wait for CI. This was merged on the user's explicit instruction to merge without waiting for builds or checks. Because it adds a schema migration, CI on
mainis the first real check of the migration, the new database tests and the upgrade path. Watch theverifyjob.Checklist
npm run checkpasses (or the part you could run is listed above) — not run; see abovedocs/contributing/documentation.md(or say why none apply)docs/security/threat-model.md(not applicable: display name only)CHANGELOG.mdGenerated by Claude Code