Ask your agent what matters now.

Second turns your meeting archive into local commands for daily briefs, meeting prep, urgent follow-ups, and deal history. Claude and Codex can use the same files you can.

$19 one-time payment

second — zsh — 80x24

Claude

Claude Code

Codex

Ollama

Use Second from Claude through MCP or the CLI. Codex, Ollama, and local agents can call the same commands, with markdown notes and JSON artifacts kept local as fallback evidence.

second handoff latest --json

One meeting. Two forms. Infinite workflows.

Every Second note is a markdown file a human can read and a structured JSON artifact an agent can act on. Same file, same folder, always local.

agent~105 tokens

second — zsh — 80x24

human~280 tokens

second — zsh — 80x24

Built-in context for real work.

Every note includes who was there, what calendar it came from, and what was decided, all in one local file. Agents do not need to piece together context from five different tabs.

meeting bundle
├─ note.md
├─ meeting.json
├─ audit.json
└─ transcript.json

Structured enough for any workflow.

Summaries, actions, attendees, and metadata live in predictable fields. Agents can query, filter, and pipe your notes into any tool, from Linear to Slack to your own scripts.

{
  "title": "Acme discovery call",
  "summary": "Budget confirmed. Demo Apr 16.",
  "actions": 3,
  "type": "sales"
}

What your agent sees.

Agent evidence commands. Each one turns your local meeting archive into context an agent can verify and act on.

second after latest --json

Latest meeting recap, decisions, questions, and next action.

second handoff latest --json

Current context packet with evidence paths.

second handoff "Acme" --json

Recent notes, actions, open questions, and next prompt.

second prep "Mark" --json

Prep for a person, account, or meeting target.

second context --person "Mark" --json

Related notes and transcript evidence.

second actions --open --urgent --json

Open actions, overdue first, with owner filters.

second trace "Acme" --json

Account or topic history across calls.

second analyze today --angle sales --json

Sales, risk, decisions, coaching, or momentum lens.

Four workflows, one command.

Prep for any meeting, analyze what happened, surface what's urgent, trace how any deal evolved. Claude can use MCP for chat workflows, and coding agents can call the same CLI against local notes.

Claude reads your meeting context through MCP or the second CLI. The local files are still there when raw evidence is needed.

second — zsh — 80x24

Let Codex do the heavy lifting with an official plugin.

Create tickets, send follow-ups, book calls, and more without leaving the Codex window.

Summarize my week. Pull Second meeting highlights, check Gmail for key threads, review Linear progress, and create a brief summary of what shipped and what's next.

5:30 PM⌘

Get started in two steps.

Enable the CLI from inside the Second app and let your agent call `second`.