feat: Add Auggie CLI engine support

[AlexFigures]

🎯 Overview

This PR adds complete integration for Auggie CLI (@augmentcode/auggie) as a new engine provider in CodeMachine.

✨ Features

• ✅ Full engine implementation with metadata, auth, execution, and telemetry modules
• ✅ Authentication via Auggie CLI session (~/.augment/session.json)
• ✅ JSON output format support with proper parsing
• ✅ Workspace-root based execution
• ✅ Immediate log file creation to prevent connection timeouts
• ✅ Comprehensive unit tests (5 tests, all passing)
• ✅ Updated README with Auggie CLI documentation

🔧 Technical Details

Engine Implementation

• Uses --print --quiet --output-format json flags for automation
• Handles Auggie's single-result JSON format: {"type":"result","result":"..."}
• Supports model override via --model flag
• Registered with order: 5 in engine registry
• Compatible with all CodeMachine workflows and orchestration patterns

Files Added

src/infra/engines/providers/auggie/
├── auth.ts                    # Authentication logic
├── config.ts                  # Configuration types
├── execution/
│   ├── commands.ts           # CLI command builder
│   ├── executor.ts           # High-level executor
│   ├── index.ts              # Module exports
│   └── runner.ts             # Core execution logic
├── index.ts                   # Engine module export
├── metadata.ts                # Engine metadata
└── telemetryParser.ts         # Telemetry parsing (placeholder)

tests/unit/infra/
└── auggie-registry.spec.ts    # Unit tests

Files Modified

• README.md - Added Auggie CLI documentation
• src/infra/engines/core/registry.ts - Registered Auggie engine
• src/infra/engines/index.ts - Exported Auggie module
• src/agents/runner/runner.ts - Fixed log file creation timing

🐛 Fixes

1. Log file creation timing - Moved log file creation to agent registration (instead of first data output) to prevent 120s timeout errors
2. Removed unused helpers - Cleaned up unused formatToolUse and formatStepEvent functions
3. Linting - All ESLint checks passing with zero warnings

✅ Testing

Unit Tests

npm test -- tests/unit/infra/auggie-registry.spec.ts

• ✅ 5/5 tests passing
• ✅ Engine registration
• ✅ Metadata validation
• ✅ Auth and run methods
• ✅ Engine ordering

Integration Testing

• ✅ Tested with real Auggie CLI
• ✅ Works with codemachine start (workflows)
• ✅ Works with codemachine run (direct execution)
• ✅ Works with orchestration (parallel & sequential)
• ✅ Log streaming works correctly
• ✅ No timeout errors

Code Quality

npm run lint    # ✅ Passing
npm run build   # ✅ Passing
npm test        # ✅ Passing

📚 Usage Examples

Workflow Configuration

{
  "agentId": "code-generation",
  "engine": "auggie",
  "model": "claude-3-5-sonnet"
}

Agent Configuration

{
  "code-generator": {
    "engine": "auggie",
    "model": "claude-3-5-sonnet"
  }
}

CLI Usage

# Authenticate
codemachine auth login
# Select "Auggie CLI"

# Run workflow
codemachine start

# Direct execution
codemachine run "code-generator 'Create a login component'"

# Engine-specific (note: requires additional fix for engine override)
codemachine auggie run "code-generator 'test'"

🔮 Future Improvements

1. Engine-specific CLI commands - Currently codemachine auggie run doesn't force Auggie engine (requires passing engine parameter through coordinator)
2. Telemetry support - Auggie doesn't return token/cost data yet; placeholder parser ready for future updates
3. Streaming support - If Auggie adds streaming in future, the parser can be extended

📝 Checklist

• Code follows project style guidelines
• All tests passing
• Linting passing (zero warnings)
• Build successful
• Documentation updated (README)
• Integration tested with real Auggie CLI
• No breaking changes
• Commit message follows conventional commits

🙏 Notes

This PR is ready for review and merge. The implementation follows the same patterns as existing engines (OpenCode, Claude, CCR) and integrates seamlessly with CodeMachine's architecture.

Tested on:

• Node.js v23.11.0
• npm 11.6.0
• Auggie CLI latest version

---

Pull Request opened by Augment Code with guidance from the PR author

[moazbuilds]

Thank you for the contribution, great work!
I'm still reviewing it, but I wanted to ask about the specific issue you encountered that required adding this part:

// Create log file immediately to prevent "Can't connect to agent" errors
// This ensures the log file exists before the engine starts producing output
loggerService.write(monitoringAgentId, ''); // Empty write to create the file

The system is supposed to wait up to 120 seconds to connect to the agent, which is a long time. So if it's still throwing a "Can't connect to agent" error after 120 seconds, understanding the root cause is important. Could you clarify what type of error you were facing that made this workaround necessary?