Skip to main content

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

Cross-platform — macOS, Linux, Windows — with terminal keybindings (Shift+Enter, word-jump, etc.) detected and configured automatically on first run, whatever terminal you're in.

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_dirbase_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. See LICENSE.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

micro_cc-0.2.47.tar.gz (3.1 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

micro_cc-0.2.47-py3-none-any.whl (3.1 MB view details)

Uploaded Python 3

File details

Details for the file micro_cc-0.2.47.tar.gz.

File metadata

  • Download URL: micro_cc-0.2.47.tar.gz
  • Upload date:
  • Size: 3.1 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.11

File hashes

Hashes for micro_cc-0.2.47.tar.gz
Algorithm Hash digest
SHA256 1586652027b9fd4945256eaf75218df7485885e6a43fad16c92297918498df66
MD5 ea40d70db3252f88e2e494cabacad64e
BLAKE2b-256 15ae4f0a2edfe4702120846f828463812f1b15d3ed89a607d57f4ce3644605fe

See more details on using hashes here.

File details

Details for the file micro_cc-0.2.47-py3-none-any.whl.

File metadata

  • Download URL: micro_cc-0.2.47-py3-none-any.whl
  • Upload date:
  • Size: 3.1 MB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.11

File hashes

Hashes for micro_cc-0.2.47-py3-none-any.whl
Algorithm Hash digest
SHA256 86a972d51dc1d4963ce91e4f9190aa742d155520082d9d289a7f95427805b2b0
MD5 2385b5ad84156c8b2625443f7740747f
BLAKE2b-256 b7add380b6a5d3449ef8219e361dc3b99949dd0be833f0daf1407552587a9d73

See more details on using hashes here.

Release history Release notifications | RSS feed

0.2.64

2 files

0.2.63

2 files

0.2.62

2 files

0.2.61

2 files

0.2.60

2 files

0.2.59

2 files

0.2.58

2 files

0.2.57

2 files

0.2.56

2 files

0.2.55

2 files

0.2.54

2 files

0.2.53

2 files

0.2.52

2 files

0.2.51

2 files

0.2.50

2 files

0.2.49

2 files

0.2.48

2 files

This release

0.2.47 This release

2 files

0.2.46

2 files

0.2.45

2 files

0.2.44

2 files

0.2.43

2 files

0.2.42

1 file

0.2.41

2 files

0.2.40

2 files

0.2.39

2 files

0.2.38

2 files

0.2.36

2 files

0.2.35

2 files

0.2.34

2 files

0.2.32

2 files

0.2.31

2 files

0.2.30

2 files

0.2.29

2 files

0.2.28

2 files

0.2.27

2 files

0.2.26

2 files

0.2.25

2 files

0.2.24

2 files

0.2.23

2 files

0.2.22

2 files

0.2.21

2 files

0.2.20

2 files

0.2.19

2 files

0.2.18

2 files

0.2.17

2 files

0.2.16

2 files

0.2.15

2 files

0.2.14

2 files

0.2.13

2 files

0.2.11

2 files

0.2.10

2 files

0.2.9

2 files

0.2.8

2 files

0.2.7

2 files

0.2.6

2 files

0.2.5

2 files

0.2.4

2 files

0.2.3

2 files

0.2.2

2 files

0.2.1

2 files

0.2.0

2 files

0.1.12

2 files

0.1.11

2 files

0.1.10

2 files

0.1.9

2 files

0.1.8

2 files

0.1.7

2 files

0.1.6

2 files

0.1.5

2 files

0.1.4

2 files

0.1.3

2 files

0.1.2

2 files

0.1.1

2 files

0.1.0

2 files

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page