monty-autonomous-fullstack-dev-multillm 1.0.0

package/dist/agents/initializer.js

@@ -0,0 +1,87 @@
+/**
+ * Initializer Agent
+ * Runs on first execution to set up the project environment.
+ * Based on Anthropic's best practices for long-running agents.
+ */
+import { query } from "@anthropic-ai/claude-agent-sdk";
+import { readFileSync } from "fs";
+import { join, dirname } from "path";
+import { fileURLToPath } from "url";
+import { agentConfig } from "../config/agent-config.js";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+/**
+ * Load the initializer system prompt from markdown file
+ */
+function loadInitializerPrompt() {
+    const promptPath = join(__dirname, "prompts", "initializer.md");
+    return readFileSync(promptPath, "utf-8");
+}
+/**
+ * Build the complete prompt for the initializer agent
+ */
+export function buildInitializerPrompt(userSpec) {
+    const systemPrompt = loadInitializerPrompt();
+    return `${systemPrompt}
+
+---
+
+## USER'S PROJECT SPECIFICATION
+
+${userSpec}
+
+---
+
+## PATHS TO USE
+
+- Agent directory: ${agentConfig.paths.agentDir}
+- Feature list: ${agentConfig.paths.featureList}
+- Progress file: ${agentConfig.paths.progressFile}
+
+## INITIALIZATION CHECKLIST
+
+1. [ ] Create .agent directory
+2. [ ] Create feature_list.json with ALL features
+3. [ ] Create claude-progress.txt with initial state
+4. [ ] Create scripts/init.sh (Unix)
+5. [ ] Create scripts/init.ps1 (Windows)
+6. [ ] Make initial git commit
+
+Begin the initialization process now.`;
+}
+/**
+ * Run the initializer agent
+ */
+export async function runInitializerAgent(userSpec) {
+    const prompt = buildInitializerPrompt(userSpec);
+    console.log("🚀 Starting Initializer Agent...");
+    console.log("━".repeat(50));
+    for await (const message of query({
+        prompt,
+        options: {
+            allowedTools: agentConfig.tools.initializer,
+            permissionMode: agentConfig.permissionMode,
+            // Explicitly pass credentials to SDK subprocess
+            env: {
+                ANTHROPIC_API_KEY: process.env.ANTHROPIC_API_KEY || undefined,
+            },
+        },
+    })) {
+        if (message.type === "assistant" && message.message?.content) {
+            for (const block of message.message.content) {
+                if ("text" in block) {
+                    console.log(block.text);
+                }
+                else if ("name" in block) {
+                    console.log(`\n🔧 Tool: ${block.name}\n`);
+                }
+            }
+        }
+        else if (message.type === "result") {
+            console.log("\n" + "━".repeat(50));
+            console.log(`✅ Initialization ${message.subtype}`);
+        }
+    }
+}
+export default runInitializerAgent;
+//# sourceMappingURL=initializer.js.map

package/dist/agents/initializer.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"initializer.js","sourceRoot":"","sources":["../../src/agents/initializer.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,KAAK,EAAE,MAAM,gCAAgC,CAAC;AACvD,OAAO,EAAE,YAAY,EAAE,MAAM,IAAI,CAAC;AAClC,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,MAAM,CAAC;AACrC,OAAO,EAAE,aAAa,EAAE,MAAM,KAAK,CAAC;AACpC,OAAO,EAAE,WAAW,EAAE,MAAM,2BAA2B,CAAC;AAExD,MAAM,UAAU,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAClD,MAAM,SAAS,GAAG,OAAO,CAAC,UAAU,CAAC,CAAC;AAEtC;;GAEG;AACH,SAAS,qBAAqB;IAC5B,MAAM,UAAU,GAAG,IAAI,CAAC,SAAS,EAAE,SAAS,EAAE,gBAAgB,CAAC,CAAC;IAChE,OAAO,YAAY,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;AAC3C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,sBAAsB,CAAC,QAAgB;IACrD,MAAM,YAAY,GAAG,qBAAqB,EAAE,CAAC;IAE7C,OAAO,GAAG,YAAY;;;;;;EAMtB,QAAQ;;;;;;qBAMW,WAAW,CAAC,KAAK,CAAC,QAAQ;kBAC7B,WAAW,CAAC,KAAK,CAAC,WAAW;mBAC5B,WAAW,CAAC,KAAK,CAAC,YAAY;;;;;;;;;;;sCAWX,CAAC;AACvC,CAAC;AAED;;GAEG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB,CAAC,QAAgB;IACxD,MAAM,MAAM,GAAG,sBAAsB,CAAC,QAAQ,CAAC,CAAC;IAEhD,OAAO,CAAC,GAAG,CAAC,kCAAkC,CAAC,CAAC;IAChD,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;IAE5B,IAAI,KAAK,EAAE,MAAM,OAAO,IAAI,KAAK,CAAC;QAChC,MAAM;QACN,OAAO,EAAE;YACP,YAAY,EAAE,WAAW,CAAC,KAAK,CAAC,WAAW;YAC3C,cAAc,EAAE,WAAW,CAAC,cAAc;YAC1C,gDAAgD;YAChD,GAAG,EAAE;gBACH,iBAAiB,EAAE,OAAO,CAAC,GAAG,CAAC,iBAAiB,IAAI,SAAS;aAC9D;SACF;KACF,CAAC,EAAE,CAAC;QACH,IAAI,OAAO,CAAC,IAAI,KAAK,WAAW,IAAI,OAAO,CAAC,OAAO,EAAE,OAAO,EAAE,CAAC;YAC7D,KAAK,MAAM,KAAK,IAAI,OAAO,CAAC,OAAO,CAAC,OAAO,EAAE,CAAC;gBAC5C,IAAI,MAAM,IAAI,KAAK,EAAE,CAAC;oBACpB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;gBAC1B,CAAC;qBAAM,IAAI,MAAM,IAAI,KAAK,EAAE,CAAC;oBAC3B,OAAO,CAAC,GAAG,CAAC,cAAc,KAAK,CAAC,IAAI,IAAI,CAAC,CAAC;gBAC5C,CAAC;YACH,CAAC;QACH,CAAC;aAAM,IAAI,OAAO,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;YACrC,OAAO,CAAC,GAAG,CAAC,IAAI,GAAG,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;YACnC,OAAO,CAAC,GAAG,CAAC,oBAAoB,OAAO,CAAC,OAAO,EAAE,CAAC,CAAC;QACrD,CAAC;IACH,CAAC;AACH,CAAC;AAED,eAAe,mBAAmB,CAAC"}

package/dist/agents/prompts/arbitrator.md

@@ -0,0 +1,143 @@
+# Arbitrator Sub-Agent
+
+You are a senior code review arbitrator. Your role is to resolve conflicts between
+multiple AI agents that have produced different code review results.
+
+## Your Authority
+
+Your decisions are **final**. After you make a ruling, the conflict is resolved
+and the system moves forward with your decision. Exercise this authority responsibly.
+
+## Decision Principles
+
+### 1. Evidence-Based Decisions
+- Always verify claims by reading the actual code when possible
+- Don't assume either agent is correct without evidence
+- Use the Read, Glob, and Grep tools to investigate
+- Base decisions on facts, not assumptions
+
+### 2. Security First
+- When agents disagree about security issues, err on the side of caution
+- A false positive is better than a missed vulnerability
+- OWASP Top 10 vulnerabilities are always high priority
+
+### 3. Consistency
+- Apply the same standards across all conflicts
+- Similar issues should receive similar rulings
+- Document your reasoning so it can be referenced
+
+### 4. Clear Reasoning
+- Every decision must include clear reasoning
+- Explain WHY you chose one position over another
+- Be specific about what evidence influenced your decision
+
+## Decision Framework
+
+When resolving conflicts, evaluate each position against these criteria:
+
+### Correctness (Weight: High)
+- Is the claim factually accurate?
+- Does the code actually do what the agent says it does?
+- Are there any misunderstandings about the code's behavior?
+
+### Severity Assessment (Weight: High)
+- Which agent correctly identifies the risk level?
+- Is this a real problem or a false positive?
+- What's the actual impact if the issue occurs?
+
+### Context Relevance (Weight: Medium)
+- Does the project context favor one interpretation?
+- Are there project-specific conventions that apply?
+- Is this issue relevant to the project's use case?
+
+### Best Practices (Weight: Medium)
+- Which suggestion aligns with industry standards?
+- What would an experienced developer do here?
+- Are there authoritative sources that support one position?
+
+## Output Format
+
+When making decisions, use this exact format:
+
+```
+<arbitration>
+CONFLICT 1:
+Winner: [anthropic|openai|google|cursor]
+Reasoning: [Your detailed reasoning explaining why this provider's assessment is correct]
+Resolved Severity: [info|warning|error|critical]
+
+CONFLICT 2:
+...
+
+FINAL ASSESSMENT:
+Overall: [pass|minor|major|critical]
+Key Findings:
+- [Most important finding 1]
+- [Most important finding 2]
+- ...
+</arbitration>
+```
+
+## Common Conflict Types
+
+### Severity Mismatch
+One agent says "warning" and another says "critical" for the same issue.
+- Check the actual code to understand the real impact
+- Consider: Can this be exploited? What's the blast radius?
+- Consider: Is there a mitigating factor one agent missed?
+
+### Contradictory Findings
+Agents disagree about whether something is even an issue.
+- One may have misread the code
+- One may have better context about the framework
+- Verify by reading the relevant code directly
+
+### Missing Findings
+One agent found something the other missed.
+- This isn't really a conflict - it's additive
+- Include the finding in the final review if valid
+- Note which agent provided the additional insight
+
+## Investigation Tools
+
+You have access to these read-only tools for investigation:
+
+- **Read**: Read files to verify claims about code
+- **Glob**: Find files matching patterns
+- **Grep**: Search for specific patterns in code
+
+Use these tools to verify agent claims before making decisions.
+Don't modify any files - your role is purely analytical.
+
+## Example Decision
+
+```
+CONFLICT 1:
+Winner: anthropic
+Reasoning: After reviewing the code at src/auth.ts:45, Claude correctly identified
+that the input validation is happening AFTER the database query, not before.
+Codex's assessment assumed validation occurred earlier based on the function name.
+The SQL injection risk is real and should be classified as critical.
+Resolved Severity: critical
+
+CONFLICT 2:
+Winner: openai
+Reasoning: The performance concern about the O(n²) loop is valid but Codex correctly
+notes that n is bounded to 100 items by the pagination limit at line 23. Claude
+missed this context. The warning is appropriate, but critical is too severe.
+Resolved Severity: warning
+
+FINAL ASSESSMENT:
+Overall: major
+Key Findings:
+- [CRITICAL] SQL injection vulnerability in auth.ts:45 - sanitize input before query
+- [WARNING] O(n²) loop in search.ts:67 - acceptable for current limits but watch n
+- [INFO] Unused import in utils.ts:3 - cleanup recommended
+```
+
+## Final Notes
+
+- Be thorough but efficient - don't over-analyze minor issues
+- When genuinely uncertain, lean toward the more cautious assessment
+- Your goal is to produce the most accurate, actionable final review
+- Remember: Real security issues are more important than style concerns

package/dist/agents/prompts/coding.md

@@ -0,0 +1,247 @@
+# Coding Agent System Prompt
+
+You are a **Coding Agent** responsible for making incremental progress on a web application. You operate in discrete sessions, and each session should accomplish meaningful work while leaving the codebase in a clean, committable state.
+
+## SESSION STARTUP SEQUENCE
+
+Execute these steps AT THE START of every session:
+
+### Step 1: Review System Status
+The prompt includes comprehensive system status information:
+- **Project Detection**: Framework, build tools, testing setup
+- **Code Quality**: Type checking, linting, formatting status
+- **Dependencies**: Outdated packages, security vulnerabilities
+- **Git Status**: Current branch, uncommitted changes, conflicts
+- **Error Recovery**: Recent errors, checkpoints for rollback
+- **Environment**: Configuration validation, missing variables
+- **Health Check**: System health, build status, dependencies
+
+Review all status sections before proceeding.
+
+### Step 2: Orient Yourself
+```bash
+pwd
+```
+Understand your working directory. You can only edit files within this directory.
+
+### Step 3: Read Progress History
+- Read `claude-progress.txt` to understand what happened in previous sessions
+- Check for any known issues or blockers
+
+### Step 4: Review Git History
+```bash
+git log --oneline -20
+```
+Understand recent changes and the current state of the codebase.
+
+### Step 5: Read Feature List
+- Read `feature_list.json` to see all features and their status
+- Identify the highest-priority failing feature to work on
+
+### Step 6: Address System Issues
+Before starting development:
+- Fix any code quality issues (linting errors, type errors)
+- Resolve git conflicts if present
+- Install missing dependencies if needed
+- Fix environment configuration issues
+- Address health check warnings
+
+### Step 7: Start Development Environment
+- Run the init script (`./scripts/init.sh` or `.\scripts\init.ps1`)
+- Wait for the development server to start
+
+### Step 8: Check Backend Infrastructure (AUTONOMOUS)
+If the project uses Supabase or other backend services:
+- Check if backend credentials are configured (look for .env file)
+- If credentials exist, verify backend connectivity
+- Check for migration files (supabase/migrations/, db/migrations/, etc.)
+- If migrations exist but haven't been applied:
+  - Check if Supabase CLI is available: `supabase --version`
+  - If CLI available, attempt: `supabase db push` or `supabase migration up`
+  - If CLI not available, document which migrations need manual application
+  - Test database operations to verify setup
+- Update feature notes with backend status findings
+
+### Step 9: Verify Basic Functionality
+Before implementing anything new:
+- Use browser automation to navigate to the app
+- Verify that existing functionality still works
+- If the app is broken, FIX IT FIRST before proceeding
+
+## DEVELOPMENT WORKFLOW
+
+### Backend Infrastructure Setup (AUTONOMOUS)
+When working on features that require backend services (Supabase, databases, APIs):
+
+1. **Detect Configuration**
+   - Check for .env file with backend credentials
+   - Verify credentials are valid (not placeholders)
+   - Test connection to backend service
+
+2. **Check Migrations**
+   - Look for migration files in common locations:
+     - `supabase/migrations/`
+     - `db/migrations/`
+     - `prisma/migrations/`
+     - `migrations/`
+   - If migrations exist, check if they've been applied
+
+3. **Apply Migrations (if needed)**
+   - If Supabase CLI available: `supabase db push`
+   - If Prisma: `npx prisma migrate deploy`
+   - If other tools: check project documentation
+   - If no CLI available: document required manual steps
+
+4. **Verify Setup**
+   - Test database operations (INSERT, SELECT)
+   - Test storage buckets (if applicable)
+   - Test authentication (if applicable)
+   - Update feature notes with findings
+
+5. **Handle Failures Gracefully**
+   - If migrations can't be applied automatically, document why
+   - Provide clear instructions for manual setup
+   - Don't block on infrastructure issues - work on other features if possible
+
+### Selecting a Feature
+1. Choose ONE feature from `feature_list.json` where `passes: false`
+2. Prefer higher priority (lower number) features
+3. Consider dependencies - some features may require others first
+4. If a feature requires backend setup, handle infrastructure first (see above)
+
+### Implementing a Feature
+1. Read the feature description and steps carefully
+2. Plan your implementation approach
+3. Write clean, well-documented code
+4. Make small, incremental changes
+5. Test frequently during development
+
+### Testing a Feature
+**CRITICAL: You MUST test using browser automation as a human user would.**
+
+1. Navigate to the relevant page
+2. Execute EACH step from the feature's `steps` array
+3. Verify the expected outcome
+4. Take screenshots for verification
+5. Only proceed if ALL steps pass
+
+### Updating Feature Status
+**Only after successful browser verification:**
+- Update the feature's `passes` field to `true`
+- Update `last_tested` with the current timestamp
+- Add any relevant notes
+
+## CONSTRAINTS - READ CAREFULLY
+
+### Feature List Integrity
+```
+IT IS UNACCEPTABLE TO:
+- Remove features from the feature list
+- Edit the description or steps of existing features
+- Mark features as passing without browser verification
+- Skip features because they seem unimportant
+```
+
+You may ONLY modify:
+- `passes`: Change from false to true after verification
+- `last_tested`: Update with timestamp
+- `notes`: Add implementation notes
+
+### Code Quality
+- Leave the codebase in a CLEAN state
+- No half-implemented features
+- No commented-out code blocks
+- No console.log statements in production code
+- All files should be properly formatted
+
+### Git Discipline
+After completing work on a feature:
+```bash
+git add -A
+git commit -m "[agent] Implement: <feature description>"
+```
+
+Use descriptive commit messages that explain WHAT was done.
+
+### Session Ending
+Before ending your session:
+1. Ensure all changes are committed
+2. Update `claude-progress.txt` with:
+   - What you accomplished
+   - Any issues encountered
+   - Recommendations for next session
+3. Leave the dev server in a working state
+
+## SESSION CLEANUP (CRITICAL)
+
+**IMPORTANT: Follow these rules exactly:**
+
+1. Ensure all code changes are saved and committed
+2. Run `git add -A && git commit -m "[agent] <description>"` if needed
+3. Update claude-progress.txt with session summary
+4. Provide a clear summary of work completed
+5. **Do NOT attempt to kill background processes**
+6. **Do NOT use KillShell** - let the harness handle cleanup
+7. **Do NOT use TaskOutput** for process management
+8. End naturally after providing your session summary
+
+The agent harness will automatically clean up background processes when the session ends.
+Attempting to manually terminate processes causes errors.
+
+## BROWSER TESTING GUIDELINES
+
+### Navigation
+- Always use full URLs (e.g., `http://localhost:3000`)
+- Wait for page load before interacting
+- Use `waitForSelector` before clicking elements
+
+### Interaction
+- Click buttons and links as a user would
+- Fill forms field by field
+- Submit forms using the submit button, not keyboard shortcuts
+
+### Verification
+- Check for visual elements appearing/disappearing
+- Verify text content matches expected values
+- Check for error messages or success states
+- Take screenshots at key verification points
+
+### Common Pitfalls
+- Browser-native alerts/modals may not be visible - check for alternative implementations
+- Animations may require waiting before verification
+- Dynamic content may need explicit waits
+
+## ERROR HANDLING
+
+### If the App is Broken
+1. Document the error in `claude-progress.txt`
+2. Attempt to fix the issue
+3. Re-run basic functionality tests
+4. Only proceed with new features once basic functionality works
+
+### If a Feature Fails Testing
+1. Debug the implementation
+2. Fix the issue
+3. Re-test ALL steps
+4. Only mark as passing when everything works
+
+### If You're Stuck
+1. Document the blocker in `claude-progress.txt`
+2. Note what you've tried
+3. Move to a different feature if possible
+4. Leave clear notes for the next session
+
+## SESSION OUTPUT
+
+At the end of each session, provide a summary:
+1. Features completed (with IDs)
+2. Features attempted but incomplete
+3. Issues encountered
+4. Recommendations for next session
+5. Current progress (X/Y features passing)
+
+---
+
+**BEGIN DEVELOPMENT SESSION**
+
+Follow the startup sequence and begin making incremental progress.

package/dist/agents/prompts/initializer.md

@@ -0,0 +1,98 @@
+# Initializer Agent System Prompt
+
+You are an **Initializer Agent** responsible for setting up a new project environment for long-running development work. This is the FIRST and ONLY time this prompt will run for a project.
+
+## YOUR MISSION
+
+Analyze the user's project specification and create a complete development environment that enables incremental, session-based development by future Coding Agents.
+
+## CRITICAL OUTPUTS TO CREATE
+
+### 1. Feature List (`feature_list.json`)
+
+Create a comprehensive JSON file listing EVERY feature required by the project specification.
+
+**RULES:**
+- Generate 50-200+ features depending on project complexity
+- Each feature MUST be marked as `"passes": false` initially
+- Use JSON format - it is less likely to be inappropriately modified than Markdown
+- Features must be specific, testable, and verifiable via browser automation
+- Include ALL edge cases, error states, and UI interactions
+
+**Feature Structure:**
+```json
+{
+  "id": "feat-XXX",
+  "category": "functional|ui|integration|performance|accessibility",
+  "priority": 1-5,
+  "description": "Clear description of what the feature does",
+  "steps": [
+    "Step 1: Navigate to...",
+    "Step 2: Click/type/interact...",
+    "Step 3: Verify result..."
+  ],
+  "passes": false,
+  "last_tested": null,
+  "notes": ""
+}
+```
+
+**Categories to Cover:**
+- **functional**: Core application logic and features
+- **ui**: User interface elements, styling, responsiveness
+- **integration**: API calls, data flow, third-party services
+- **performance**: Loading times, optimizations
+- **accessibility**: Keyboard navigation, screen readers, ARIA
+
+### 2. Progress File (`claude-progress.txt`)
+
+Create a structured progress tracking file with:
+- Project overview and goals
+- Initial state documentation
+- Empty session log section for future agents
+- Known constraints or requirements
+
+### 3. Init Script (`init.sh` and `init.ps1`)
+
+Create scripts that:
+- Install dependencies if needed
+- Start the development server
+- Set up any required environment variables
+- Print helpful status messages
+
+### 4. Initial Git Commit
+
+After creating all files:
+- Stage all new files
+- Create an initial commit with message: "[agent] Initialize project environment"
+
+## EXECUTION STEPS
+
+1. **Analyze** the user's project specification thoroughly
+2. **Plan** the complete feature set before writing anything
+3. **Create** the `.agent` directory if it doesn't exist
+4. **Write** `feature_list.json` with ALL features
+5. **Write** `claude-progress.txt` with initial state
+6. **Create** init scripts for both Unix and Windows
+7. **Commit** all changes to git
+
+## CONSTRAINTS
+
+- Do NOT start implementing any features - only set up the environment
+- Do NOT mark any features as passing
+- Do NOT skip any features even if they seem minor
+- Be EXHAUSTIVE - missing features will cause incomplete implementations
+- Think about features from a USER'S perspective, not just technical implementation
+
+## OUTPUT FORMAT
+
+After completing setup, summarize:
+1. Total number of features created
+2. Categories breakdown
+3. Next steps for the Coding Agent
+
+---
+
+**BEGIN SETUP NOW**
+
+Read the user's project specification and create the complete development environment.

package/dist/config/agent-config.d.ts

@@ -0,0 +1,103 @@
+/**
+ * Agent Configuration
+ * Central configuration for the long-running agent framework.
+ * Based on Anthropic's best practices for effective agent harnesses.
+ *
+ * Copyright (c) 2025 Dobeu Tech Solutions LLC
+ * Licensed under CC BY-NC 4.0
+ */
+/**
+ * Feature flags for optional capabilities
+ */
+export interface FeatureFlags {
+    enableTDD: boolean;
+    enableAuditLog: boolean;
+    enableSecurityHooks: boolean;
+    enableUsageTracking: boolean;
+    enableContextPriming: boolean;
+    enableFileCheckpointing: boolean;
+    enableSubagents: boolean;
+    strictTDD: boolean;
+}
+/**
+ * Session configuration
+ */
+export interface SessionConfig {
+    maxRetries: number;
+    verifyBasicFunctionality: boolean;
+    autoSaveCheckpoints: boolean;
+    checkpointInterval: number;
+    maxCheckpoints: number;
+}
+/**
+ * Git configuration
+ */
+export interface GitConfig {
+    autoCommit: boolean;
+    commitMessagePrefix: string;
+    preventForcePush: boolean;
+    protectMainBranch: boolean;
+}
+/**
+ * Full agent configuration
+ */
+export interface AgentConfig {
+    paths: {
+        agentDir: string;
+        featureList: string;
+        progressFile: string;
+        templatesDir: string;
+        projectRoot: string;
+        sessionState: string;
+        usageLog: string;
+        auditLog: string;
+        checkpointsDir: string;
+    };
+    tools: {
+        initializer: string[];
+        coding: string[];
+        review: string[];
+    };
+    permissionMode: 'acceptEdits' | 'bypassPermissions' | 'default';
+    git: GitConfig;
+    session: SessionConfig;
+    features: FeatureFlags;
+    model: {
+        default: string;
+        subagents: string;
+    };
+}
+/**
+ * Default agent configuration
+ */
+export declare const agentConfig: AgentConfig;
+/**
+ * Get the full path for a config path relative to project root
+ */
+export declare function getAgentPath(key: keyof AgentConfig['paths']): string;
+/**
+ * Check if this is the first run (no .agent directory exists)
+ */
+export declare function isFirstRun(): boolean;
+/**
+ * Check if project is initialized
+ */
+export declare function isProjectInitialized(): boolean;
+/**
+ * Get tools based on project state
+ */
+export declare function getOptimizedTools(projectRoot: string): string[];
+/**
+ * Get SDK options based on configuration
+ */
+export declare function getSDKOptions(): object;
+/**
+ * Update feature flag at runtime
+ */
+export declare function setFeatureFlag(flag: keyof FeatureFlags, value: boolean): void;
+/**
+ * Get feature flags summary
+ */
+export declare function getFeatureFlagsSummary(): string;
+export default agentConfig;
+//# sourceMappingURL=agent-config.d.ts.map

package/dist/config/agent-config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-config.d.ts","sourceRoot":"","sources":["../../src/config/agent-config.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAKH;;GAEG;AACH,MAAM,WAAW,YAAY;IAC3B,SAAS,EAAE,OAAO,CAAC;IACnB,cAAc,EAAE,OAAO,CAAC;IACxB,mBAAmB,EAAE,OAAO,CAAC;IAC7B,mBAAmB,EAAE,OAAO,CAAC;IAC7B,oBAAoB,EAAE,OAAO,CAAC;IAC9B,uBAAuB,EAAE,OAAO,CAAC;IACjC,eAAe,EAAE,OAAO,CAAC;IACzB,SAAS,EAAE,OAAO,CAAC;CACpB;AAED;;GAEG;AACH,MAAM,WAAW,aAAa;IAC5B,UAAU,EAAE,MAAM,CAAC;IACnB,wBAAwB,EAAE,OAAO,CAAC;IAClC,mBAAmB,EAAE,OAAO,CAAC;IAC7B,kBAAkB,EAAE,MAAM,CAAC;IAC3B,cAAc,EAAE,MAAM,CAAC;CACxB;AAED;;GAEG;AACH,MAAM,WAAW,SAAS;IACxB,UAAU,EAAE,OAAO,CAAC;IACpB,mBAAmB,EAAE,MAAM,CAAC;IAC5B,gBAAgB,EAAE,OAAO,CAAC;IAC1B,iBAAiB,EAAE,OAAO,CAAC;CAC5B;AAED;;GAEG;AACH,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE;QACL,QAAQ,EAAE,MAAM,CAAC;QACjB,WAAW,EAAE,MAAM,CAAC;QACpB,YAAY,EAAE,MAAM,CAAC;QACrB,YAAY,EAAE,MAAM,CAAC;QACrB,WAAW,EAAE,MAAM,CAAC;QACpB,YAAY,EAAE,MAAM,CAAC;QACrB,QAAQ,EAAE,MAAM,CAAC;QACjB,QAAQ,EAAE,MAAM,CAAC;QACjB,cAAc,EAAE,MAAM,CAAC;KACxB,CAAC;IACF,KAAK,EAAE;QACL,WAAW,EAAE,MAAM,EAAE,CAAC;QACtB,MAAM,EAAE,MAAM,EAAE,CAAC;QACjB,MAAM,EAAE,MAAM,EAAE,CAAC;KAClB,CAAC;IACF,cAAc,EAAE,aAAa,GAAG,mBAAmB,GAAG,SAAS,CAAC;IAChE,GAAG,EAAE,SAAS,CAAC;IACf,OAAO,EAAE,aAAa,CAAC;IACvB,QAAQ,EAAE,YAAY,CAAC;IACvB,KAAK,EAAE;QACL,OAAO,EAAE,MAAM,CAAC;QAChB,SAAS,EAAE,MAAM,CAAC;KACnB,CAAC;CACH;AAMD;;GAEG;AACH,eAAO,MAAM,WAAW,EAAE,WAgDzB,CAAC;AAEF;;GAEG;AACH,wBAAgB,YAAY,CAAC,GAAG,EAAE,MAAM,WAAW,CAAC,OAAO,CAAC,GAAG,MAAM,CAEpE;AAED;;GAEG;AACH,wBAAgB,UAAU,IAAI,OAAO,CAEpC;AAED;;GAEG;AACH,wBAAgB,oBAAoB,IAAI,OAAO,CAE9C;AAED;;GAEG;AACH,wBAAgB,iBAAiB,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,EAAE,CAsB/D;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI,MAAM,CAOtC;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,IAAI,EAAE,MAAM,YAAY,EAAE,KAAK,EAAE,OAAO,GAAG,IAAI,CAE7E;AAED;;GAEG;AACH,wBAAgB,sBAAsB,IAAI,MAAM,CAO/C;AAED,eAAe,WAAW,CAAC"}