Skip to content

feat(plan): resolve planner agent per-request via AgentRegistry#82

Merged
alxsuv merged 1 commit into
mainfrom
feat/79-per-request-planner-agent
May 20, 2026
Merged

feat(plan): resolve planner agent per-request via AgentRegistry#82
alxsuv merged 1 commit into
mainfrom
feat/79-per-request-planner-agent

Conversation

@alxsuv

@alxsuv alxsuv commented May 20, 2026

Copy link
Copy Markdown
Member

Remove hardcoded _planning_agent (gemini-2.5-pro) from HensuFactory. LlmPlanner now takes AgentRegistry instead of a singleton Agent, resolving the planner per-request from PlanningConfig.agentId with fallback to the node's own agent. Adds agentId field to PlanningConfig, PlanRequest, and RevisionContext. Exposes agent property and dynamic(plannerAgent) in the Kotlin DSL.

Resolve: #79

Remove hardcoded _planning_agent (gemini-2.5-pro) from HensuFactory. LlmPlanner now takes AgentRegistry instead of a singleton Agent, resolving the planner per-request from PlanningConfig.agentId with fallback to the node's own agent. Adds agentId field to PlanningConfig, PlanRequest, and RevisionContext. Exposes agent property and dynamic(plannerAgent) in the Kotlin DSL.

Resolve: #79
Signed-off-by: Aleksandr Suvorov <asuvorov@hensu.io>
@alxsuv alxsuv merged commit ab13d37 into main May 20, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Remove binding of default planner to particular model

1 participant