micro · cc — cognitive compute
88
""
88,dPYba,,adPYba, 88 ,adPPYba, 8b,dPPYba, ,adPPYba, ,adPPYba, ,adPPYba,
88P' "88" "8a 88 a8" "" 88P' "Y8 a8" "8a a8" "" a8" ""
88 88 88 88 8b 88 8b d8 · 8b 8b
88 88 88 88 "8a, ,aa 88 "8a, ,a8" "8a, ,aa "8a, ,aa
88 88 88 88 `"Ybbd8"' 88 `"YbbdP"' `"Ybbd8"' `"Ybbd8"'
Knowledge work is, by extension, a coding problem.
Frontier models with full system access — shell, filesystem, browser, MCP. Verbose, thorough planning paired with unrestricted file operations lets micro·cc take on complex multi-step work autonomously. Point it at any project directory and go.
Install
pip install micro-cc
Supported platforms: macOS and WSL (Windows Subsystem for Linux) — both are real POSIX/bash environments, which the bash_ tool requires. Terminal keybindings (Shift+Enter, word-jump, etc.) are detected and configured automatically on first run, whatever terminal you're in.
Windows: install WSL first (wsl --install in PowerShell, then reboot), then run pip install micro-cc inside the WSL shell — not in PowerShell/cmd directly. Native Windows isn't supported: there's no bash, and the desktop-control tool depends on macOS-only APIs anyway, so nothing is lost by going through WSL.
Usage
microcc /path/to/your/project
First run, type /login and pick Anthropic, a LiteLLM proxy (Bedrock, Azure, etc.), or Ollama — it writes ~/.micro-cc/.env for you, no manual editing needed.
Controls:
Enter— submit ·Shift+Enter— newline ·Escape— interrupt/login— configure endpoint ·/model— switch model ·/clear— reset conversation ·/keys— store project-scoped secrets ·/exit— quit- Type
/to see the full command list (setup, skills, MCP, headless, batch, etc.)
Headless (-p mode / cron)
microcc-headless /path/to/project_dir "Fix the JWT expiry bug — tokens aren't refreshing correctly."
The microcc equivalent of claude -p — one prompt (argument or piped via stdin), no manifest to write first. project_dir scopes the conversation exactly like the interactive TUI does, so pointing repeated cron runs at the same dir continues that history; a fresh dir starts stateless. Runs fully autonomously (no approval gate), so it never blocks waiting on stdin — a clarifying question from the model is auto-cancelled rather than hung on.
It prints the outcome the same way batch does — STATUS: DONE|NEEDS_INPUT|FAILED — <summary> parsed into a symbol + the full reply:
✓ DONE — Patched JWT expiry check in auth.py
<full reply body, if any, above the status line>
Useful flags: -f/--file (repeatable, points the prompt at specific files), --output-format json (machine-parseable {status, summary, body, project_dir}), --verbose (streams tool calls/results to stderr — handy in cron logs).
Batch (multi-task / cron)
microcc-batch /path/to/base_dir tasks.json
For running several named tasks in one go, each kept in its own isolated subfolder so context never bleeds between them — reach for this over microcc-headless when you want that separation. Each task gets its own subfolder under base_dir — base_dir/{task.name}/ — which is a real project_dir with its own scoped messages.jsonl. Runs are fully autonomous (no approval gate), so a batch never blocks waiting on stdin. To pick a task back up in the full interactive TUI:
cd base_dir/{task.name} && microcc .
Manifest format (tasks.json):
{
"tasks": [
{
"name": "fix-auth-bug",
"prompt": "Fix the JWT expiry bug — tokens aren't refreshing correctly.",
"files": ["/absolute/path/to/src/auth.py", "/absolute/path/to/src/middleware.py"]
},
{
"name": "add-tests",
"prompt": "Add unit tests for the pagination helper."
}
]
}
files is optional and must use absolute paths — cron jobs have no reliable cwd.
Tasks run sequentially. Each is instructed to end its final reply with STATUS: DONE|NEEDS_INPUT|FAILED — <summary>, which the runner parses into a tree view at the end:
/path/to/base_dir
├── ✓ fix-auth-bug DONE Patched JWT expiry check in auth.py
├── ? add-tests NEEDS_INPUT Which test framework does this repo use?
└── ✓ cleanup-logs DONE Removed dead logging branches
2/3 done · 1 need input · 0 failed
cd into: /path/to/base_dir/add-tests (then `microcc .` to continue)
Only tasks that failed or need input get a cd hint — no need to open every subfolder to check on a large batch.
Data
~/.micro-cc/
.env API keys
projects/
{project}_{hash}/
messages.jsonl conversation history
summary.json sliding-window summary
project_path.txt maps hash back to directory
Tools
| Tool | Description |
|---|---|
bash_ |
Shell execution in project_dir |
read_ |
Read files with line numbers, offset/limit |
write_ |
Create/overwrite files, auto-creates dirs |
edit_ |
Surgical string replacement (fails if ambiguous) |
glob_ |
Find files by pattern, sorted by mtime |
grep_ |
Regex search with context lines |
browser_ |
Web browsing and page extraction (beta) |
computer_use_ |
Screen interaction and GUI automation (beta) |
All tools are discoverable — use search_tools to find more at runtime.
Relative paths resolve to project_dir. Absolute paths work anywhere.
License
Proprietary — all rights reserved.
1 maintainer
Release files for micro-cc 0.2.68
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| micro_cc-0.2.68.tar.gz | 3.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| micro_cc-0.2.68-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.5 MB
Release files / micro_cc-0.2.68.tar.gz
| Download URL | micro_cc-0.2.68.tar.gz |
|---|---|
| Size | 3.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb4c5e43d89811c52d029c58c573ec8b62a3b748906679e38f6f110932fe532e
|
|
BLAKE2b-256 checksum How to use checksums |
87a08ff1a4acdf352d096edb7e361673bd5518cc0d3f672722ff6725c1b75010
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / micro_cc-0.2.68-py3-none-any.whl
| Download URL | micro_cc-0.2.68-py3-none-any.whl |
|---|---|
| Size | 3.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a784511f5be8c8ce341e56fbad438533a2cd190e30667f4e0056c2a3fb565ce4
|
|
BLAKE2b-256 checksum How to use checksums |
a63d55dd9926becf1365e58d2712bf03b8ffc88402785e964c459d433be49e12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
