Iiwi

Iiwi · /ˈiː.wiː/ "ee-wee"

Turn your AI coding work into clear engineering reports.

English | 繁體中文

You already did the work. Iiwi turns the history left by your coding agents into an update you can review and share.

Iiwi works with OpenCode, Claude Code, and Codex. It finds what you worked on, keeps related work together, and turns it into a Markdown report without making you reread old agent conversations.

• Works across projects. Iiwi finds your coding-agent sessions wherever you worked.
• Keeps related work together. Sessions are grouped by repository.
• You stay in control. Choose and edit what belongs in the final report.
• Protects sensitive information. Common secret patterns are removed before reports are written.

How it works

1. Read — Iiwi finds local AI coding history from OpenCode, Claude Code, or Codex.
2. Review — Keep, edit, reorder, or remove the work that matters.
3. Generate — Create a Markdown report you can share with your team.

What you get

A reviewed report can look like this:

# Weekly engineering update

## My Project
- Simplified the report workflow and made review easier to use.
- Added Claude Code and Codex session support.
- Fixed documentation checks in CI.

## Blockers
- None

Quick start

Requires Python 3.11+ and git.

• Reads from: local session history from OpenCode, Claude Code, or Codex.
• Drafts with: the CLI matching whatever it read — opencode, claude, or codex.
• No CLI installed? Use --no-llm for a simpler structured report.

Reading Claude Code or Codex history does not need their CLI tools, but drafting does. Set narrator.provider to draft with a different CLI than the one you read from.

pipx install iiwi                 # or: pip install iiwi

iiwi doctor                       # check your setup
iiwi daily                        # review yesterday, today, and blockers
iiwi report --period last-week    # write last week's report

Reports are written under reports/ by default. Add --dry-run to preview a report in the terminal without writing a file.

The interactive menu

Run iiwi with no arguments if you would rather use a menu than remember flags. The main menu gives you Review Activity, Daily Standup, Generate Report, History, Check Setup, and Settings. Use iiwi --help when you want the full command list.

Generate Report lets you choose the report settings, review the sessions Iiwi found, and then generate the report. Review Sessions shows the work grouped by repository so you can quickly keep or exclude what belongs in the update:

Review Sessions   6 / 6 selected │ 252 / 252 msgs
══════════════════════════════════════════════════════
Select sessions to include in the report:

  1. ▾ ████████████  71% ● iiwi   3 / 3    Aug 5 │ 180 msgs
▶      ████░░░░░░░░  24% ● Add the interactive menu Aug 5 │ 60 msgs
       ████░░░░░░░░  24% ● Redact before writing    Aug 5 │ 60 msgs
       ████░░░░░░░░  24% ● Group worktrees          Aug 5 │ 60 msgs
  2. ▸ ████░░░░░░░░  24% ● obsidian-wiki   2 / 2    Aug 4 │ 60 msgs
  3. ▸ █░░░░░░░░░░░   5% ● dotfiles   1 / 1         Aug 3 │ 12 msgs

↑↓ jk │ ←→ hl │ Space Toggle │ p Preview │ e Exclude │ a All │ g Generate │ / Search │ ? Help │ b Back

Daily Standup, or iiwi daily, opens a Yesterday / Today / Blockers review for recent work. History lists reports Iiwi has already written.

Before a report is written, Quick Review lets you keep, edit, reorder, split, or add work items so the final Markdown reflects what you actually want to share. For the full keyboard flow, report modes, and recovery behavior, see the Quick Review guide. For Daily Standup details, see the Daily Standup guide.

Commands

iiwi doctor                       # check your setup
iiwi daily                        # review yesterday, today, and blockers
iiwi scan --period last-week      # preview the sessions Iiwi found
iiwi report --period last-week    # write last week's report
iiwi history                      # list reports already written
iiwi update                       # check PyPI for a newer release
iiwi run                          # use the step-by-step wizard

iiwi --help lists every command and option. Use iiwi run if you prefer a step-by-step wizard; for scripts, call the subcommand you need directly.

Configuration

Settings come from an environment variable first, then the settings file, then the default:

iiwi config init                                          # walk through all
iiwi config set harnesses.opencode.cli.model deepseek-r1  # write one
iiwi config list                                          # show all, with sources
iiwi config unset report.timezone                         # back to the default

Every setting and its environment-variable name is in the configuration guide.

Privacy

Session reading, redaction, and report generation stay on your machine. Iiwi passes the redacted session text to a CLI you already have installed — opencode, claude, or codex — and no API key is required. iiwi update is the command that checks the network for a newer release on PyPI.

Reports can still contain private goals, filenames, commands, and full working paths, so review a report before sharing it. See Privacy and security for the full data flow and current limits.

Documentation

The name

The ʻiʻiwi is a scarlet Hawaiian honeycreeper whose long curved bill reaches nectar others cannot — which is what this tool does with the sessions your agent left behind. Pronounced the anglicised way, "ee-wee".

Development

git clone https://github.com/mike840609/iiwi.git
cd iiwi
uv sync --locked --extra dev                    # install the project and its dev tools

uv run iiwi                                     # run your working copy
uv run pytest --cov=iiwi --cov-fail-under=80    # tests, with the coverage gate CI enforces
uv run ruff check .                             # lint
uv run pyright                                  # type check

The last three are exactly what CI runs, so a green local run means a green PR.

Name forms

The name is cased by where it appears:

License

MIT