tomcounsell/ai
tomcounsell
Python17updated 4mo ago
Python17updated 4mo agoA productive AI coworker that learns, self-improves, and ships work.
ClaudeCodexCursorMCP
agent-harnessagentic-workflowsaiai-agentautonomous-agentclaude-codellm-agentmcptelegram
README
Valor
An autonomous AI coworker. Not an assistant, not a chatbot — a colleague that owns its own machine and does real work.
Why Valor?
- Works where you work. Receives tasks via Telegram or Email and replies in the same thread — no context switching, no dashboards to check.
- Ships code end-to-end. Plans a feature, critiques the plan, writes the code, runs tests, opens a PR, and merges it — without being babysat through each step.
- Remembers across sessions. A subconscious memory system injects relevant past decisions and corrections as
<thought>blocks at exactly the right moment. - Fixes itself. A watchdog + self-healing pipeline restarts on crashes, hibernates on API failures, and escalates to you only when automation can't recover.
- Extensible by design. Add a new skill in
.claude/skills/, wire a tool intools/+ MCP, or connect a new comms channel inbridge/— the architecture absorbs extensions without surgery.
What Is This?
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.
How It Works
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).