Skip to main content

Iiwi

Iiwi · /ˈiː.wiː/ "ee-wee" — turns your coding-agent sessions into a weekly engineering report, without anything leaving your machine.

CI Release PyPI Python License: MIT PRs Welcome Ask DeepWiki

English | 繁體中文

Iiwi — see what your agents did

The weekly status update is work you already did once. Iiwi reads the sessions your coding agent already recorded, synthesizes evidence-backed outcomes, and lets you review the result before it writes the report. Quick Review targets a 30–60 second pass from candidate outcomes to a shareable update. Works with OpenCode, Claude Code, and Codex.

  • Nothing leaves your machine. Your local opencode run writes the narrative — no network, no API key.
  • Finds your sessions anywhere. Every project, whichever folder you run from.
  • Groups by repository. Worktrees collapse into one entry; child and subagent sessions stay with it.
  • Redacts first. Common secret patterns are stripped locally before anything is written.

Quick start

Needs Python 3.11+ and git. Plus one transcript source: OpenCode (the default, needs an opencode executable) or a readable Claude Code / Codex transcript store at ~/.claude/projects or ~/.codex (their CLIs are not needed for reading). Quick Review outcome synthesis still uses your local opencode run for every transcript source; if it is unavailable, the recovery screen offers Retry and an explicit session-based report fallback.

pipx install iiwi                 # or: pip install iiwi

iiwi doctor                       # is the harness ready?
iiwi daily                        # review yesterday, today, and blockers
iiwi report --period last-week    # write the report

The report lands under reports/. Pass --dry-run to print the report to the terminal instead of writing a file.

The interactive menu

Run iiwi with no arguments if you would rather not remember flags:

$ iiwi
 ___ _        _
|_ _(_)_ __ _(_)
 | || \ V  V / |
|___|_|\_/\_/|_|                                v0.9.1
══════════════════════════════════════════════════════
Turn coding-agent sessions into engineering reports
github.com/mike840609/iiwi

▶ Review Activity
  Daily Standup
  Generate Report
  History
  Check Setup
  Settings                       # full-screen editor, every choice listed

↑↓ jk │ Enter Select │ 1-6 │ ? Help │ q Quit

Choosing Generate a report shows every setting at once instead of asking one question at a time — ↑↓ moves, ←→ changes a value, and a line under the list explains the setting you are on. Press g to generate, or r to open Review sessions first, which weighs each repository by how much of the period it actually accounts for:

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

Choosing History lists every report the tool has written, newest first. ↑↓ moves; Enter shows the row's full output path.

Choosing Daily Standup, or running iiwi daily, scans every enabled harness from yesterday's local midnight through now and opens a three-section Quick Review for Yesterday, Today, and Blockers. Preview and Generate use the same reviewed Markdown, written as daily-standup-YYYY-MM-DD.md. See the Daily Standup guide for source warnings, suggested Today work, and same-day review persistence.

Space toggles a repository or a single session, p previews a transcript (redacted), and e excludes a repository from every future scan. Your selection is remembered per period. Press g to synthesize the selected sessions into Quick Review instead of writing the session-based report immediately.

Quick Review keeps the evidence traceable while you decide what belongs in the update. The first five candidates are selected; additional work stays under More candidates, and extraction failures stay visible under Ungrouped candidates. User-added outcomes, optional Blockers, and optional Next week text are included in the same in-memory draft.

Space Include/exclude │ e Edit │ J/K Reorder │ v Evidence │ s Split │ a Add
p Preview │ g Generate │ b Back

p Preview renders the current draft without writing a file. g Generate writes that reviewed draft. If synthesis fails, retry it or explicitly use the labeled session-based report fallback. See the evidence-first Quick Review guide for the full flow and the Manager/Engineering and Brief/Full responsibilities.

Commands

iiwi doctor                       # is the harness ready?
iiwi daily                        # review yesterday, today, and blockers
iiwi scan --period last-week      # preview how sessions group
iiwi report --period last-week    # write the report
iiwi history                      # reports already written
iiwi update                       # check PyPI for a newer release
iiwi run                          # the same questions, one at a time
Flag What it does
--harness claude-code / --harness codex Read another harness's sessions — the narrative still comes from your local opencode run
--no-llm Deterministic structured report; works whether or not OpenCode is installed
--sanitize OpenCode's stronger redaction, which intentionally removes most work evidence
--dry-run Print the report instead of writing a file
--json Redacted machine-readable output for scan, doctor, history, and update (the default when stdout is piped)

iiwi --help lists everything, and run is the linear wizard if you prefer being asked. In scripts, name a subcommand directly — with no terminal to prompt at, the menu exits with status 3 rather than reading stdin.

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

Everything happens on your machine: sessions are read from disk, common secret patterns are redacted, and the redacted transcript is handed to your locally installed opencode run. No API key, and update is the only command that touches the network.

Reports may still contain private goals, filenames, commands, and full working paths — always review one before sharing it. See Privacy and security for the full data flow and current limits.

Documentation

Page What's in it
CLI reference Every command, option, and exit code
Daily Standup Yesterday/Today/Blockers review, refresh, warnings, and output
Evidence-first Quick Review Outcome review keys, report modes, recovery, and current exclusions
Configuration Settings file, environment variables, precedence
Privacy and security Data flow, redaction boundary, what reports still contain
Security policy Threat model and how to report a vulnerability
Usage guides Reporting periods, subagents, repository grouping, output handling
Usage statistics How the usage section is built, and its window caveat
Support and limits The per-harness caveat list
Architecture How a report is produced, end to end
Releasing How a release is cut

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:

Context Form
Distribution, CLI, URLs, application directories iiwi
Python package and imports iiwi
Prose Iiwi
Environment variables IIWI_ prefix
Error base class IiwiError

License

MIT

Metadata

Release files for iiwi 0.14.0

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

Source distribution (sdist)

Source distribution for iiwi 0.14.0
File Size Uploaded Provenance
iiwi-0.14.0.tar.gz 2.4 MB With provenance Details

Built distribution (wheel)

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

Total release size: 2.6 MB

Release files / iiwi-0.14.0.tar.gz

Download URL iiwi-0.14.0.tar.gz
Size 2.4 MB
Tags Source
SHA-256 checksum
How to use checksums
4f93439917a1a0da20227fe0d35acac25672925303c233b59a46336a5b273872
BLAKE2b-256 checksum
How to use checksums
728387d407b2fd20dcf2d3cd621cf7b9839f79a3622aa8fd88deb199f0444a81
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Release files / iiwi-0.14.0-py3-none-any.whl

Download URL iiwi-0.14.0-py3-none-any.whl
Size 178.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c8e59b72a949f67b2829f9d94ca76b67e9e8354d7c06517cae17529b0238f9cc
BLAKE2b-256 checksum
How to use checksums
43972d3895d0268544d682538c71c6b4c1b46afa4f6c1ffdc7ea94a7be456754
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Security for iiwi 0.14.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for iiwi-0.14.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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