App-qualified agent ids - #454
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
force-pushed
the
app-qualified-agent-ids
branch
from
September 6, 2026 12:43
6b7c0a8 to
5f6053f
Compare
An agent declared on an App takes `<app>.<attribute>` as its id, the way a workflow's kind takes `<app>.<kind>`. The registry key, the override keys, the profile lookup, the timeline's agent, the step name, and the settings wire all carry that one name, so two apps can declare the same attribute name. A standalone agent with an explicit id keeps it. Migration d2f7a9c4e816 rewrites the bundled apps' override rows to the qualified key. A row for another app's agent keeps its flat key.
The projection sent the declared display name as `name`, which the pages use as the settings key. A named agent's model save answered "Unknown agent" and its effort save landed under a key nothing reads. `name` is the id; the display name, else the attribute name, is `label`.
czpython
force-pushed
the
app-qualified-agent-ids
branch
from
September 6, 2026 14:49
5229c74 to
dd9113f
Compare
czpython
enabled auto-merge (squash)
September 6, 2026 14:50
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
1 participant
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.
An agent declared on an App takes
<app>.<attribute>as its id:software_factory.file_tickets. This is the ruleWorkflow.kindalready follows. The id is the one durable name, so the registry key, theagent_*:override keys,get_profile,AgentCall.agent, the DBOS step name, and the settings wire carry it with no further change. Two apps can now declare the same attribute name. A standalone agent with an explicitid=keeps it. App code does not change: an author still writesfile_tickets = Agent(...)and callsawait BugHunter.file_tickets(...).The id itself is qualified, not the registry key alone, because the profile lookup, the override keys, the timeline, and the settings PATCH body would each need a second name otherwise.
The settings wire carries the id as
nameand the declared display name, else the attribute name, aslabel. The pages show the label and key their edits by the id.Migration
d2f7a9c4e816rewrites the bundled app's override rows to the qualified key and its recorded agent steps indbos.operation_outputsto the qualified step name, so a retried run replays under the names the code now uses. The database does not record which app declares an agent, and a migration cannot read the app registry, so an override or a recorded step of any other app's agent keeps its flat name. Set the override again in Settings → Apps.Historic
agent_calls.agentvalues stay as recorded. They are display-only, and the timeline label derives the same word from the flat and the qualified name.🤖 Generated with Claude Code