RedPlanetHQ / RedPlanetHQ/core
Deprecate source and introduce agent as mcp connected to agents, agent makes more sense than source
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 194
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
Proposal: Deprecate the use of 'source' and introduce 'agent' as the canonical term for MCP-connected entities. Rationale: The term 'agent' more accurately reflects the architectural role and future extensibility of these components compared to 'source'.
- Update all references of 'source' to 'agent' across the codebase, documentation, and integration APIs.
- Ensure all MCP connections and orchestration flows reference 'agent'.
- Update migration and onboarding flows to use 'agent' terminology exclusively.
Context: This aligns with ongoing terminology standardization and will improve clarity for all users and developers working with MCP and agent orchestration.
Please triage, assign, and label as appropriate for architecture/API refactor.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by mapping the existing “source” terminology across the codebase, documentation, integration APIs, MCP connections, orchestration, migration, and onboarding flows; done means these references consistently use “agent”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100