bmaltais / bmaltais/orchestrator
MVP-4: Build orchestrator CLI
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Problem
Need a CLI interface for:
- Submitting tasks to the orchestrator
- Monitoring task progress
- Retrieving results
- Managing agent sessions
## Requirements
1. Create CLI with subcommands:
- `orchestrator submit ` - Submit a new task
- `orchestrator status ` - Check task status
- `orchestrator results ` - Get task results
- `orchestrator list` - List all tasks
- `orchestrator monitor ` - Real-time monitoring
2. Connect to Redis for task queue
3. Connect to LiteLLM for model routing
4. Connect to GitHub for PR creation
5. Support configuration via `~/.orchestrator/config.yaml`
## Implementation Plan
1. Create Python CLI structure
2. Implement Redis client integration
3. Implement LiteLLM client integration
4. Implement GitHub API integration
5. Add configuration management
6. Add error handling and logging
## Acceptance Criteria
- CLI can submit tasks
- CLI can monitor task progress
- CLI can retrieve results
- Configuration is manageable
- Error handling is robust
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names the orchestrator CLI subcommands and ~/.orchestrator/config.yaml but no existing files or tests. Start by inspecting the repository structure and current entry points, then trace how task, Redis, LiteLLM, and GitHub integrations are organized. Done means all listed commands, configuration management, monitoring, results retrieval, and robust error handling work end to end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python, redis, yaml
- Domain
- backend, cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100