rem_help

co rem help pages

Each section is printed verbatim by --help for the command it names. The agreed design is issue #1656; change a page there and here together.

co rem

co rem — a notebook about the people, projects and tools in your work, kept up to date from your mail and coding sessions.
Experimental: a preview; its commands may change before 1.9.0.

Build (once)
  init          Build the notebook from 90 days of mail and sessions, then write your page.
  investigate   Fill a page, a whole category, or your own page, using a model.
Read
  open          Browse the notebook in your browser.
  list          List pages in a category (people, projects, orgs, skills).
  show          Print one page.
  search        Find text across pages. No model.
Keep it current
  start         Approve sources and turn on the daily schedule.
  stop          Turn the schedule off. Pages and approvals stay.
  status        Is the schedule on, when it runs next, what ran today.
  sync          Run one update now.
Settings
  sources       Which mailboxes, coding tools and chats the notebook reads.
  config        Model, schedule times and limits.
  logs          What each run did, and what it cost.
  doctor        Check that everything the notebook needs is installed.

Options (before the command):
  --root DIR    The notebook folder (default ~/.co/rem).
  --json        Machine-readable output: {"ok", "data", "next"}.

First time:   co rem init
Example:      co rem search "term sheet" --in people
Every page:   co rem <command> --help
Advanced:     co rem advanced --help   (scan, map-skills, stub, reflect, reflections,
              propose, review, abstract, capture, projects)
Old names:    unfinished, people, daily, subscriptions, subscribe, unsubscribe, route
              and usage still work until 1.9.0 and print their new name.

co rem init

Build the notebook and investigate what matters now. One command.

First the map is made without a model: a page for each person you write to, each organization,
each coding project and each installed Skill, plus your own page, titled with your
name and filled with who you write to most and where you work. init prints that
page when the map is done. It lists 90 days of mail headers, the preview line your
provider lists with each message (to name people by your greeting), saved
contacts, and session metadata, then saves a private copy of each listed message
body, once, so investigating a person later reads it from disk.

Then it writes your own page by itself from everything you sent
and your coding sessions of the last 30 days (co rem investigate me): a quick
first pass in about 4 minutes, then the whole page alongside the rest. It also
investigates eligible people, those active in the last 14 days first (up to two years of
their mail), projects (recent first), organizations linked to those people,
and installed skills from their source instructions and retained run evidence,
12 pages at a time. The result should let you recognize useful relationships
and work immediately, with evidence cited on each page.
--first-people, --first-projects, --first-orgs and --first-skills cap a kind (0 for none).
Before the first page it says one total: about how many pages, ~how many billed
input tokens on your plan and ~how many minutes, an estimate from the median of
this notebook's own runs (before there are any, measured defaults). It names the
runner and model. Around 20% of a weekly runner allowance is a target,
not a hard limit: the selected investigation finishes even if it uses more.
The configured weekly safety floor still stops new pages when measurable.
Ctrl-C stops it, says which pages were written, and
keeps the map and every page. It is skipped, with the reason, when the runner is missing
or signed out, when no mailbox gave an address of yours, or when your page was
already written. More people: co rem investigate people. More projects: co rem
projects write.

Usage:    co rem init [--days N] [--mine ADDRESS[,ADDRESS...]] [--name NAME] [--mail gmail|outlook]...
                       [--no-mail-archive] [--investigate | --no-investigate]
                       [--first-people N] [--first-projects N] [--first-orgs N] [--first-skills N]
Example:  co rem init --days 90 --name "Aaron Xie" --mine [email protected],[email protected]

Inputs:   Connected mailboxes (co auth google, co auth microsoft) and local Codex /
          Claude Code sessions. --mine adds addresses that are yours (commas, or
          repeat it). Addresses that look like yours are listed on one line, with
          one command that confirms the ones you keep.
Options:  --investigate     Explicitly request the default investigation.
          --no-investigate  Build the map only.
          --first-people N    Cap eligible people (default all selected; 0 for none).
          --first-projects N  Cap queued projects (default all selected; 0 for none).
          --first-orgs N     Cap related organizations (default all selected; 0 for none).
          --first-skills N   Cap installed skill investigations (default all mapped; 0 for none).
Output:   Your page's facts and where it is; one progress line per stage on stderr
          (every step in .state/init-progress.log); pages under ~/.co/rem (or
          --root); private files under .state/: source-inventory.md and .jsonl
          (what was listed, window by window), and mail/ (one body per message,
          per-person and per-project indexes). A seven-day window at the
          200-message listing cap is split until all of it is listed. Mail bodies
          never go into a page and never leave this machine. Re-running keeps
          anything written and reuses saved bodies.
Effects:  Writes pages and private files (owner-only). Reads mail bodies unless
          --no-mail-archive. Mailboxes it read are subscribed for the daily round;
          nothing is read in the background until co rem start is approved. The
          map costs nothing; the subsequent investigation uses the configured
          model for the selected people, projects and organizations. No schedule.
Takes:    About 10 minutes to map 90 days of two mailboxes; saving bodies takes
          longer; investigation time depends on the selected pages and runner.
          An interrupted run resumes where it stopped.

Next:     co rem open   (read your page), then co rem start (keep it current)
Back:     co rem --help