
Security News
Frontier AI Is Now Critical Infrastructure
The Fable shutdown shows how quickly model access can become a business continuity risk for AI-dependent engineering teams.
The Problem: Claude Code is incredibly powerful, but you can only work on one thing at a time with a single claude code instance. This kills true multitasking and orchestration.
Our Belief: AI should scale with your ambition, not limit it. Why use only one Claude instance?
The Vision: Transform your machine or dedicated server into an AI powerhouse where you orchestrate multiple Claude Code instances through one main session. Work on authentication in repo A while simultaneously building APIs in repo B, all coordinated through your primary Claude Code interface - no context pollution, no workflow interruption.
See FEATURES.md for complete feature list.
claude command available)Minimum (for development/testing):
Recommended (for production):
Add to your project's .mcp.json:
{
"mcpServers": {
"claudine": {
"command": "npx",
"args": ["-y", "claudine", "mcp", "start"]
}
}
}
Restart Claude Code to connect to Claudine.
Once configured, use these tools in Claude Code:
| Tool | Description | Usage |
|---|---|---|
| DelegateTask | Submit tasks to background instances | DelegateTask({ prompt: "...", priority: "P1" }) |
| TaskStatus | Get real-time task status | TaskStatus({ taskId }) |
| TaskLogs | Stream or retrieve execution logs | TaskLogs({ taskId }) |
| CancelTask | Cancel tasks with resource cleanup | CancelTask({ taskId, reason }) |
| Command | Description |
|---|---|
claudine mcp start | Start the MCP server |
claudine delegate <task> | Submit new task |
claudine status [task-id] | Check task status (all tasks if no ID) |
claudine logs <task-id> | View task output |
claudine cancel <task-id> | Cancel running task |
claudine help | Show help |
Create workflows where tasks wait for dependencies to complete:
# Step 1: Create build task
claudine delegate "npm run build" --priority P1
# → task-abc123
# Step 2: Create test task that waits for build
claudine delegate "npm test" --depends-on task-abc123
# Task waits for build to complete before running
# Step 3: Create deploy task that waits for tests
claudine delegate "npm run deploy" --depends-on task-def456
# Execution order: build → test → deploy
Multiple dependencies (parallel execution):
// lint and format run in parallel
const lint = await DelegateTask({ prompt: "npm run lint" });
const format = await DelegateTask({ prompt: "npm run format" });
// commit waits for both to complete
const commit = await DelegateTask({
prompt: "git commit -m 'Formatted and linted'",
dependsOn: [lint.taskId, format.taskId]
});
See Task Dependencies Documentation for advanced patterns (diamond dependencies, error handling, failure propagation).
Event-driven system with autoscaling workers and SQLite persistence. Components communicate through a central EventBus, eliminating race conditions and direct state management.
Task Lifecycle: Queued → Running → Completed / Failed / Cancelled
See Architecture Documentation for implementation details.
| Variable | Default | Range | Description |
|---|---|---|---|
TASK_TIMEOUT | 1800000 (30min) | 1000-86400000 | Task timeout in milliseconds |
MAX_OUTPUT_BUFFER | 10485760 (10MB) | 1024-1073741824 | Output buffer size in bytes |
CPU_THRESHOLD | 80 | 1-100 | CPU usage threshold percentage |
MEMORY_RESERVE | 1073741824 (1GB) | 0+ | Memory reserve in bytes |
LOG_LEVEL | info | debug/info/warn/error | Logging verbosity |
Override limits for individual tasks:
// Long-running task with larger buffer
await DelegateTask({
prompt: "analyze large dataset",
timeout: 7200000, // 2 hours
maxOutputBuffer: 104857600 // 100MB
});
// Quick task with minimal resources
await DelegateTask({
prompt: "run eslint",
timeout: 30000, // 30 seconds
maxOutputBuffer: 1048576 // 1MB
});
npm run dev # Development mode with auto-reload
npm run build # Build TypeScript
npm start # Run built server
npm run typecheck # Type checking
npm test # Run tests
npm run clean # Clean build artifacts
npm test # Run all tests (safe, sequential)
npm run test:coverage # Run with coverage
npm run test:unit # Unit tests only
npm run test:integration # Integration tests only
npm run validate # Validate entire setup
claudine/
├── src/
│ ├── core/ # Core interfaces and types
│ ├── implementations/ # Service implementations
│ ├── services/ # Business logic & event handlers
│ ├── adapters/ # MCP adapter
│ ├── bootstrap.ts # Dependency injection
│ ├── cli.ts # CLI interface
│ └── index.ts # Entry point
├── dist/ # Compiled JavaScript
├── tests/
│ ├── unit/ # Unit tests
│ └── integration/ # Integration tests
└── docs/ # Documentation
See ROADMAP.md for detailed plans and timelines.
Ensure claude CLI is in your PATH:
which claude
Check logs in stderr and verify Node.js version:
node --version # Should be v20.0.0+
Run in development mode to see detailed logs:
npm run dev
Contributions are welcome! Please read our contributing guidelines before submitting PRs.
MIT License - see LICENSE file for details
Built with the Model Context Protocol SDK
FAQs
MCP server for delegating tasks to Claude Code
We found that claudine demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
The Fable shutdown shows how quickly model access can become a business continuity risk for AI-dependent engineering teams.

Security News
AI agents are pulling packages into environments no scanner is watching, creating exposure before security teams can see it.

Security News
GitHub Actions checkout now blocks risky pull_request_target checkouts by default to help prevent pwn request supply chain attacks.