mirror of
https://github.com/andy-stack/vaultkeeper-ai.git
synced 2026-07-22 16:30:27 +00:00
Restructure the AI workflow from a single-agent model to a specialized multi-agent system with distinct roles: - Add AgentType enum (Main, Orchestration, Planning, Execution) to define agent specializations - Replace AIControllerService and AIFunctionService with modular agent classes in Services/AIServices/: - MainAgent: Handles user interaction and delegates to orchestration - OrchestrationAgent: Coordinates plan execution and step-by-step workflow - PlanningAgent: Creates and revises execution plans - ExecutionAgent: Executes individual plan steps - AIController: Base class providing common agent loop functionality - Create specialized prompts (OrchestrationPrompt, ExecutionPrompt) for agent-specific behavior - Add OrchestrationResult type to communicate workflow control decisions (continue, abort, replan) - Introduce agent-specific function scoping: - ExecuteWorkflow for main agent - CompleteTask for execution agent - CompleteStep/Replan/CancelPlan for orchestration agent - SubmitPlan/AskUserQuestionPlanning for planning agent - Update BaseAIClass to use agentType property instead of isPlanningAgent boolean for model selection - Simplify ExecutionPlan and ExecutionStep types by removing execution state tracking (moved to agent coordination) - Remove PlanningEnabledAppendix and ExecutionStatus enum (superseded by agent architecture) - Add comprehensive integration tests for agent workflows This architecture provides better separation of concerns, clearer agent responsibilities, and more robust plan execution with explicit orchestration control flow.
22 lines
No EOL
1,009 B
TypeScript
22 lines
No EOL
1,009 B
TypeScript
import { AIFunction } from "Enums/AIFunction";
|
|
import type { IAIFunctionDefinition } from "../IAIFunctionDefinition";
|
|
|
|
export const CompleteStep: IAIFunctionDefinition = {
|
|
name: AIFunction.CompleteStep,
|
|
description: `Signals that plan execution should proceed to the next step without modification.
|
|
|
|
- Use this tool when the most recent step completed successfully and its results align with the plan's expectations.
|
|
- This is the appropriate choice when everything is working as intended and no course correction is needed.
|
|
- Do NOT use this if there were any failures, unexpected results, or if the plan needs adjustment based on new information.`,
|
|
parameters: {
|
|
type: "object",
|
|
properties: {
|
|
confirm_completion: {
|
|
type: "boolean",
|
|
description: "Safety flag that must be explicitly set to true to confirm the step completion is intentional. This prevents accidental completions.",
|
|
default: false
|
|
}
|
|
},
|
|
required: ["confirm_completion"]
|
|
}
|
|
} |