Crow
An Agent Development Environment (ADE) for building, running, and improving autonomous coding agents.
Status: In active development. Phase 0 complete (ACP server, iterative refinement, task pipeline). See ROADMAP.md for what's next.
What is Crow?
Crow is NOT just an ACP server, NOT just an IDE. It's a complete environment where:
- Humans plan in a journal (Logseq-inspired knowledge base)
- Humans + agents prime the environment together (pair programming)
- Autonomous agents work in the primed environment (read journal → write code → document decisions)
- Humans review in the journal and provide feedback
- Knowledge accumulates and agents get better over time
Quick Start
Installation
Install the Crow CLI globally:
cd /home/thomas/src/projects/orchestrator-project/crow
uv build
uv tool install dist/crow_ai-0.1.2-py3-none-any.whl --python 3.12
This installs the crow command globally, available from any directory.
Configuration:
- API keys and secrets:
~/.crow/.env - User settings:
~/.crow/config.yaml - Sessions:
~/.crow/sessions/ - Logs:
~/.crow/logs/
Usage
Start the ACP server:
crow acp
Using with ACP clients:
uv --project /path/to/acp-python-sdk run python acp-python-sdk/examples/client.py crow acp
Other commands:
crow # Show help
crow --version # Show version
Reinstalling After Changes
cd /home/thomas/src/projects/orchestrator-project/crow
uv build
uv tool install dist/crow_ai-0.1.2-py3-none-any.whl --python 3.12
Development Setup
For development work on Crow itself:
cd /home/thomas/src/projects/orchestrator-project/crow
uv --project crow sync
See AGENTS.md for detailed development workflow instructions.
Documentation
- INSTALLATION.md - Installation and configuration guide
- DESIGN.md - Vision, architecture, and design decisions
- CURRENT_STATE.md - Analysis of current code and what needs fixing
- ROADMAP.md - Development phases and timeline
- AGENTS.md - Project-specific knowledge for agents
- REFACTOR_PLAN.md - Original refactor plan (superseded by ROADMAP.md)
Features
Current (Phase 0 - Complete)
- ✅ ACP Server - Streaming ACP server wrapping OpenHands SDK
- ✅ Iterative Refinement - Planning → Implementation → Critique → Documentation loop
- ✅ Task Pipeline - Split PLAN.md into tasks, run sequentially
- ✅ MCP Integration - playwright, zai-vision, fetch, web_search
- ✅ Session Management - Multiple concurrent sessions with persistence
- ✅ Slash Commands - /help, /clear, /status
In Progress (Phase 1-3)
- 🚧 Restructure - Moving files from root to
src/crow/ - 📋 Jinja2 Templates - Replace hardcoded prompts with templates
- 📋 Environment Priming - Human + agent pair programming before autonomous phase
Planned (Phase 4-8)
- 📋 Project Management -
/projects/directory, git repos, journals - 📋 Journal Page - Logseq-inspired knowledge base
- 📋 Web UI - CodeBlitz/Monaco integration
- 📋 Feedback Loops - Capture human feedback, feed to agents
- 📋 Telemetry - Self-hosted Laminar/Langfuse
Architecture
Crow
├── ACP Server (src/crow/agent/)
│ └── Streaming ACP protocol implementation
├── Orchestration (src/crow/orchestration/)
│ ├── Environment priming
│ ├── Task splitting
│ ├── Iterative refinement
│ └── Task pipeline
├── Web UI (Future)
│ ├── CodeBlitz/Monaco editor
│ ├── Journal page
│ ├── Project browser
│ └── Terminal
└── Projects (/projects/)
└── Each project = git repo + journal
The Problem We're Solving
Current AI coding tools:
- ❌ Drop agents into empty workspaces (no context)
- ❌ Lose agent decisions in markdown files ("lost like tears in rain")
- ❌ No feedback loop (human review not captured)
- ❌ No knowledge accumulation
Our solution:
- ✅ Environment priming - Human + agent set up context first
- ✅ Journal - All decisions documented and linked
- ✅ Feedback loops - Human review captured and fed back
- ✅ Knowledge accumulation - Agents get better over time
Contributing
This is a personal project, but feedback and ideas are welcome!
License
MIT
Acknowledgments
- Agent Client Protocol
- OpenHands SDK
- Model Context Protocol
- Trae Solo - Autonomous development inspiration
- Google Antigravity - Agent-first IDE inspiration
- Logseq - Knowledge management inspiration
- CodeBlitz - Web IDE foundation
"The agent is the primary developer, humans are the critics/product managers."
Modified with Crow ADE
Metadata
Release files for crow-ai 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| crow_ai-0.2.3.tar.gz | 7.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crow_ai-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.3 MB
Release files / crow_ai-0.2.3.tar.gz
| Download URL | crow_ai-0.2.3.tar.gz |
|---|---|
| Size | 7.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67821473c66ef8196909f5208c109445b6b2837c94e15a5e142d2bca3efc8bbc
|
|
BLAKE2b-256 checksum How to use checksums |
8c4a8a750d5a67cb8db7c8fe8b7af973a3a118c45ed848f2c49ce4e729eb5e27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 1, 2026.
Transparency logRelease files / crow_ai-0.2.3-py3-none-any.whl
| Download URL | crow_ai-0.2.3-py3-none-any.whl |
|---|---|
| Size | 6.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c86883c1a9d044b9ca08e076ffab3d9f037e27243b64f6f17fac28060d060da8
|
|
BLAKE2b-256 checksum How to use checksums |
dfe722bf55f235ec4e1efb669f87591d5053bd697fbb4cb9889fc5a225690879
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 1, 2026.
Transparency log