Rename Assistants to Teammates#1835
Open
mistercrunch wants to merge 3 commits into
Open
Conversation
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.
Summary
Big-bang rename of Agor's product entity from Assistant/Assistants to Teammate / AI teammate across product surfaces.
This PR intentionally treats the rename as a pre-1.0 breaking change where useful, while preserving cheap compatibility for legacy serialized state, routes, docs redirects, and framework detection.
Highlights
TeammateConfig,isTeammate,getTeammateConfig) while keeping deprecated assistant aliases for cheap compatibility.primary_teammate_idin schema/repository/API surfaces./guide/teammatescanonical;/guide/assistantsremains a legacy redirect-style page.assistantterminology for chat message roles, provider events, SDK event parsing, and other true LLM protocol contexts.Compatibility / migrations
custom_context.teammate.kind = 'teammate'.custom_context.assistantandcustom_context.agentwhere cheap.boards.primary_assistant_idtoprimary_teammate_id.primary_teammate_idand keeps the legacyprimary_assistant_idcolumn as compatibility to avoid a destructive local table rebuild; repository reads fall back to the legacy value./guide/assistantspoints users to/guide/teammates.preset-io/agor-assistantremains while canonical copy points atpreset-io/agor-teammate.Validation
pnpm ipnpm checkpnpm --filter @agor/core test -- src/templates/assistant-welcome-note.test.ts src/db/repositories/boards.test.tspnpm --filter agor-ui test -- src/utils/assistantWelcomeNote.test.ts src/components/BranchModal/BranchModal.test.tsxpnpm --filter @agor/daemon test -- src/mcp/tools/knowledge.test.ts src/services/branches.test.ts src/services/boards.test.ts src/services/assistant-knowledge.test.tsNotes
pnpm icompleted successfully;node-ptylogged a native build fallback becausemakeis unavailable in this environment.assistanthits should primarily be intentional protocol/model-role references, deprecated compatibility aliases, or historical redirect artifacts.