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.2

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.2
File Size Uploaded Provenance
mainai-0.3.2.tar.gz 27.6 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 46.4 kB

Release files / mainai-0.3.2.tar.gz

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

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

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

Security for mainai 0.3.2

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