Skip to main content

mainai

A CLI that figures out which coding agent (Claude Code, Codex, Grok, ...) last did real work in a project folder, and hands off cleanly to the one you pick next.

The problem

Working the same project folders with several coding agents means that coming back months later, it's unclear which agent did the most recent real work, and what the other agents did in the meantime.

What it does

$ mainai .
Found 6 session(s) in /home/user/projects/endotypes
  codex    2026-09-25  "fix the endotype clustering..."   <- latest work
  claude   2026-09-18  "add the GSE cohort loader..."
  ...

Continue with: codex (its edits match the files on disk; the Claude sessions
were read-only questions)
  Advice: cd /home/user/projects/endotypes && codex

$ mainai --handoff .
...
Wrote /home/user/projects/endotypes/HANDOFF.md
  1. Reads every agent's stored conversations, keeps the ones for the given folder.
  2. Decides which agent to continue with. An LLM reads each session's actual content (not just the newest timestamp) and recommends one, with its reasoning printed alongside the pick.
  3. Prints advice: the command to run to continue with that agent. mainai never launches anything itself.

The folder argument is required (mainai . for the current directory) -- mainai with no arguments prints help and does nothing, so a stray bare invocation after install never spends tokens or bills an API key unasked.

Flags: --list (sessions + a free file-evidence guess only, no LLM call, no file written), --agent NAME (override the pick, no LLM call), --handoff (also summarize the other agents' sessions into HANDOFF.md, one extra LLM call), --handoff-agents grok[,codex,...] (summarize only the named agent(s) instead of every agent other than the one picked -- implies --handoff; e.g. continue with Claude via --agent claude while still pulling in context from Grok via --handoff-agents grok), -y/--yes (skip the confirmation before an LLM call that would bill ANTHROPIC_API_KEY directly, when no claude.ai subscription login is found).

See mainai.md for the full design notes (reader architecture, per-agent log formats, picker logic, summarizer, scope/build order).

Status

Readers for Claude Code, Codex, and Grok, the LLM-based picker, --handoff, and the CLI are implemented. Published to PyPI as mainai.

Development

uv-managed project.

uv sync
uv run mainai --list .

Metadata

Release files for mainai 0.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mainai 0.3.1
File Size Uploaded Provenance
mainai-0.3.1.tar.gz 19.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for mainai 0.3.1
File Interpreter ABI Platform
mainai-0.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 38.4 kB

Release files / mainai-0.3.1.tar.gz

Download URL mainai-0.3.1.tar.gz
Size 19.6 kB
Tags Source
SHA-256 checksum
How to use checksums
a1bbca80b5ea91abcf57c22f828102376d91fa9a707058aa8d66732db3be0188
BLAKE2b-256 checksum
How to use checksums
dfaf9a2aee32728843b34d6776547048d47de2b00a257cdb05460497e009fda3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.4

Release files / mainai-0.3.1-py3-none-any.whl

Download URL mainai-0.3.1-py3-none-any.whl
Size 18.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8916628feee4eb6a9e1b5dd01ebbe22b4e0841bed12e2fdb534c84b49a585996
BLAKE2b-256 checksum
How to use checksums
87dc3ba7871c7792e9fa580faaf62c7aafd5acd4d0d83a9d76e4e928a7a207ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.4

Security for mainai 0.3.1

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page