Repository navigation
feat: add named agent types with API and CLI support for v1.4.0 - #26
Abdullahbinmushtaq wants to merge 5 commits into
Conversation
|
The CI parser setup issue has been resolved, and all five checks now pass: lint, tests on Python 3.10, 3.11, and 3.12, and MongoDB lazy-loading integration. |
|
The latest commit fixes arXiv compatibility, Wikipedia requests, Yahoo Finance news fallback, and Gemini response handling. All five GitHub CI checks have passed. Local verification also passed 151 tests on each Python 3.10, 3.11, and 3.12, including integration coverage. Live Gemini and six tools were verified; Tavily remains unverified because its API key was unavailable. The verification report is included in docs/live_tool_verification.md. Ready for maintainer review. |
This PR adds purpose-specific bot configurations through
create_bot(..., agent_type=...), the existing HTTP build endpoint, and the CLI. Developers can select research, coding, financial, or customer support behavior while retaining existing RAG and legacy agent usage.Changes
AgentTypeRegistrywith four built-in types.agent_typeselection,longtrainer build [BOT_ID], andbot create --agent-type.1.4.0, and remove the tracked internal roadmap.Compatibility and scope
Existing method parameters, API routes, response shapes, and legacy CLI commands remain supported. Older bot records require no migration.
Named tool lists replace defaults, including explicit empty lists. Customer support uses document-grounded RAG and rejects web/upload augmentation. Coding and financial Python tools execute in-process.
YAML remains infrastructure-only. SQL is deferred pending safety and configuration review. Tagging and package publication are outside this PR.
Local validation
1.4.0.Live external search/finance responses were not tested. Remote CI and maintainer review remain pending.