An autonomous AI coworker. Not an assistant, not a chatbot ā a colleague that owns its own machine and does real work.
Valor wraps agent harnesses (like Claude Code) and bridges them to the comms channels humans actually use (Telegram, Email, LinkedIn, and more). The supervisor assigns work and provides direction. Valor executes autonomously on its own Mac, reaching out when necessary.
Three layers:
- Comms layer ā bridges to the channels where work actually happens: Telegram, Email, LinkedIn, etc. Messages come in, replies go out, session context survives across conversations.
- Harness layer ā wraps agent harnesses like Claude Code, giving Valor tools, memory, skills, and a full SDLC workflow.
- Execution layer ā a standalone worker service runs sessions against the configured harness. Sessions come in three role flavors: PM (orchestrates work), Dev (writes code), and Teammate (conversational).
See docs/features/bridge-worker-architecture.md for the full design.
Valor ships real features through a structured pipeline, each stage a skill the agent invokes:
Plan ā Critique ā Build ā Test ā Patch ā Review ā Docs ā Merge
A PM session steers the pipeline and delegates coding work to a Dev session. See .claude/skills/sdlc/SKILL.md for the ground truth on stage definitions.
| Subsystem | Purpose |
|---|---|
| Subconscious memory | Long-term memory with bloom-filter recall, intentional saves, and post-session extraction |
| Reflections | Daily autonomous maintenance pipeline (log review, audits, cleanup, reporting) |
| Autoexperiment | Nightly prompt optimization for observer/summarizer targets |
| Self-healing | Watchdog service with crash tracking and automatic recovery |
| Session steering | Inject guidance into running sessions from any process |
| Worktree isolation | Per-feature git worktrees for parallel work without collisions |
| Dashboard | Web UI showing sessions, health, reflections, and machine state |
# 1. Install dependencies
pip install -e .
# 2. Configure environment
cp .env.example .env
# Edit .env with your API keys and comms credentials
# 3. Start the bridge and worker
./scripts/start_bridge.sh
./scripts/valor-service.sh worker-start./scripts/valor-service.sh status # Bridge status
./scripts/valor-service.sh restart # Restart bridge after code changes
./scripts/valor-service.sh worker-status # Worker status
./scripts/valor-service.sh worker-restart # Restart worker
tail -f logs/bridge.log # Stream logsai/
āāā agent/ # Session queue, SDK client, output routing
āāā bridge/ # Comms bridges (Telegram, etc.) and nudge loop
āāā worker/ # Standalone worker service (python -m worker)
āāā tools/ # Local Python tools
āāā ui/ # Dashboard web UI
āāā monitoring/ # Watchdog, crash tracker, health checks
āāā .claude/
ā āāā skills/ # SDLC and utility skills
ā āāā commands/ # Slash commands
ā āāā agents/ # Subagent definitions
āāā config/ # SOUL.md persona, projects.json
āāā scripts/ # Service management, setup, deployment
āāā docs/features/ # Feature-level documentation
āāā tests/ # Unit, integration, e2e
pytest tests/unit/ -n auto # Fast unit tests in parallel
pytest tests/ # Full suite
python -m ruff format . # Format| Resource | Purpose |
|---|---|
| CLAUDE.md | Development principles and working guide |
| docs/features/README.md | Feature index ā how things work |
| config/SOUL.md | Valor persona and philosophy |
| tests/README.md | Test suite index and contribution guide |
