Initializes a new AutoBeAgent instance with the specified configuration.
Creates and configures the agent with AI vendor settings, behavioral context (locale/timezone), and compilation infrastructure. The agent can optionally resume from previous conversation histories to continue development sessions or build upon existing work.
The constructor sets up the internal MicroAgentica engine, initializes the development state from provided histories, and establishes the event dispatch system for real-time progress notifications. The agent becomes ready for conversation-driven development immediately after construction.
Configuration properties including AI vendor settings, behavioral context, compilation tools, and optional conversation histories for session continuation
Engages in conversation with the agent to drive the vibe coding process.
Accepts user input in multiple formats including simple text strings, single multimodal content items, or arrays of content supporting text, images, file uploads, and audio input. The conversation serves as the primary interface for expressing requirements, providing feedback, and guiding the development process through natural language interaction.
The agent analyzes the conversation context to determine appropriate actions, potentially activating specialized agents (Analyze, Database, Interface, Test, Realize) through function calling based on user needs. Real-time progress events are fired through registered listeners while the conversation processes.
Returns all history records generated during this conversation turn, including user messages, assistant responses, and any development activities triggered by the interaction. This enables clients to track both conversational flow and development progress.
User input as text, single content item, or multimodal array
Promise resolving to array of history records from this conversation
Retrieves all generated files from the current development session.
Transforms the development process into deployable artifacts including requirements documentation, database schemas, API specifications, NestJS implementation code, and test suites. The generated files represent a fully functional backend application ready for deployment.
Optionaloptions: IAutoBeGetFilesOptionsConfiguration specifying database system and code generation preferences
Promise resolving to file paths mapped to complete file contents
Retrieves the complete conversation and development history.
Returns chronologically ordered record of all events including user messages, assistant responses, development activities, and progress events. This history enables conversation replay and development process analysis.
Array of all history records from session start
Retrieves the current development phase in the vibe coding pipeline.
Returns the active phase of the AutoBE development process, indicating which agent is currently executing or which stage of backend generation is in progress. This information is useful for tracking overall pipeline progress, displaying phase-specific UI elements, and coordinating multi-phase operations.
The phase information updates in real-time as the agent progresses through the waterfall development model, transitioning from analyze through database, interface, test, and realize phases. When no phase is active (before starting or after completion), returns null.
Current AutoBePhase enum value indicating the active development phase, or null when no phase is currently executing
Retrieves comprehensive AI token usage statistics for the current session.
Returns detailed breakdown of token consumption across all specialized agents and processing phases, enabling cost monitoring and performance analysis. Includes aggregate totals and component-specific breakdowns.
Token usage statistics with breakdowns by agent and operation type
Unregisters a previously registered event listener.
Removes the specified listener from the notification system. The listener function reference must exactly match the function originally registered with on for successful removal.
Event type the listener was registered for
The exact listener function reference to remove
This instance for method chaining
Registers an event listener for specific development phase events.
Enables real-time notifications about conversation flow, development progress, and completion events. The type-safe event system ensures listeners receive properly typed events corresponding to their registration type.
Event type to listen for
Callback function receiving the typed event when fired
This instance for method chaining
Main agent class that orchestrates the entire vibe coding pipeline through conversation-driven development.
The AutoBeAgent serves as the central coordinator for the waterfall-based development process with spiral model iterative improvements. It manages the five specialized agents (Analyze, Database, Interface, Test, Realize) that transform user conversations into complete working applications through a sophisticated AST-based compilation infrastructure.
The agent operates through natural language conversation, supporting multimodal input including text, images, files, and audio. It maintains conversation history, tracks development progress through real-time events, and provides access to all generated artifacts including requirements documentation, database schemas, API specifications, test suites, and implementation code.
The vibe coding approach eliminates traditional development barriers by enabling users to express requirements naturally while the agent handles all technical implementation details through validated AST transformations and continuous quality assurance feedback loops.
Author
Samchon