ArchitectureHow It Works

Docs v0.1.0Local-first flow

upd CLI runs entirely on your machine. Your codebase stays private; only commit metadata is formatted and optionally sent to Slack.

Visual Flow Diagram

STEP 01

Scan Local Git History

upd runs standard git log across repos under your configured work directory. Only commit messages and repo names are collected — never source code or diffs.

STEP 02

Format via Your AI CLI

Raw commits are passed to the AI engine you chose (Codex, Claude, Gemini, Grok, Ollama, or a custom CLI template) using an optimized standup prompt.

STEP 03

Review, Save & Deliver

Copy to clipboard, edit in your editor, save a daily draft file, or post to Slack via the Web API (chat.postMessage) as yourself — no bot badge.

Agent workflow (optional)

When Claude, Codex, or Cursor runs upd for you, the flow splits generation and delivery: prepare saves a dated markdown file, you review it, then send slack posts the saved text without re-running AI.

Read the AI Agents guide →

Why This Model is Highly Secure

Unlike SaaS tools that connect to your GitHub organization in the cloud, upd operates strictly client-side. Your repositories are scanned locally; commit logs are filtered on your machine before any AI CLI is invoked.

Slack delivery uses your personal User OAuth token (xoxp-) and chat.postMessage — not incoming webhooks — so messages appear under your real name and avatar.