Skip to main content
command CX Codex

obsidian-catchup — Claude Code command: process your capture queue

obsidian-catchup — a command to review everything you dumped into the Telegram journal bot on the go—voice, text, images, PDFs, links—and integrate it into your Obsidian vault with Claude Code when you're back at the laptop.

MIT ★ 5,412 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain
Open on GitHub

What obsidian-catchup does

Bridges the gap between fast, dumb capture on your phone and deliberate integration on your laptop. The Telegram bot fills a catchup.md file in your vault root; each line holds a timestamp, capture type (voice, text, image, PDF, link), and summary. The command reads that queue, shows unprocessed items grouped by age (today, this week, older), and walks you through what to do with each one.

Processing happens with you in the loop: Claude Code proposes a move (integrate into an existing note, keep as-is, discard), you confirm or redirect. Once decided, the item gets checked off in catchup.md with today's date. Every note created or updated follows references/ai-first-rules.md—proper frontmatter with type and tags, ai-first: true, wiki links for people and projects, sources preserved. Items older than a week are flagged explicitly so you can let go of stale material.

Filter by time with an argument: today (this day only), week (past 7 days), all (all unprocessed, the default). At the end you get a one-line summary: N integrated, M discarded, K left waiting.

What it helps with

  • process phone captures without drowning in inbox
  • weave material into your vault following structure rules
  • surface stale notes so you can let them go
  • keep a record of what arrived without losing history
  • stay hands-on while Claude Code handles the routine

Example prompts for the agent

  • Process everything waiting in my Telegram catchup
  • Show me what I captured this week
  • Go through today's captures from the queue

How to install obsidian-catchup

1Plugin marketplace

/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain

2Manually: put the files in place

.claude/commands/obsidian-catchup.md

Call it with /obsidian-catchup. For all projects use ~/.claude/commands/

Questions about obsidian-catchup

How do I install obsidian-catchup in Claude Code?

Run these commands in order: /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain, and add the file .claude/commands/obsidian-catchup.md to your project.

What does obsidian-catchup do?

It reads your capture queue from the Telegram bot (text, voice, images, PDFs, links) stored in catchup.md, displays unprocessed items grouped by age, and helps you decide whether to integrate each into your vault, keep it as-is, or discard it.

Can I filter the queue by date?

Yes—pass today to see only today's captures, week for the past 7 days, or all for all unprocessed items (the default).

Source text

obsidian-catchup.md · MIT
---
description: Review and process everything captured on the go from the Telegram journal bot - voice, text, images, PDFs, links - waiting in the catchup queue. You pull it when you are back at the laptop; nothing is processed autonomously.
category: vault
triggers_en: ["catch up", "catchup", "what did I dump from telegram", "process my captures", "go through my telegram dumps", "anything new from the phone", "process my catchup", "review what I captured", "what did I capture on the go"]
triggers_de: ["Rückstand aufarbeiten", "kurz auf den neuesten Stand bringen", "was habe ich aus Telegram gespeichert", "meine Notizen verarbeiten", "meine Telegram-Ablage durchgehen", "gibt es etwas Neues vom Handy", "meinen Rückstand verarbeiten", "durchsehen, was ich festgehalten habe", "was habe ich unterwegs festgehalten"]
triggers_es: ["ponme al día", "qué mandé por telegram", "procesa mis capturas", "revisa lo que capturé desde el móvil", "hay algo nuevo del móvil", "repasa mi cola de capturas"]
triggers_pt: ["coloque em dia", "catchup", "o que eu despejei do telegram", "processe minhas capturas", "passe pelas minhas capturas do telegram", "tem algo novo do telefone", "processe meu catchup", "revise o que capturei", "o que capturei na correria"]
triggers_zh: ["看看我从手机记了什么", "处理 Telegram 收集箱", "整理我路上记的东西", "整理待处理的随手记录", "把最近随手记的内容过一遍"]
---

Use the obsidian-second-brain skill. Execute `/obsidian-catchup $ARGUMENTS`:

The optional argument is a timeframe filter: `today`, `week`, or `all` (default: `all` unprocessed).

This is the laptop-side companion to the Telegram journal bot (`integrations/telegram-journal/`). The bot captures on the go (voice / text / image / PDF / link) and appends each one to a `catchup.md` queue in the vault. This command is where those captures become real, integrated vault knowledge - on your schedule, with you driving. It is a PULL: nothing was processed automatically, so nothing surprises you.

1. Read `_CLAUDE.md` first if it exists in the vault root (for vault paths + conventions).
2. Read `catchup.md` in the vault root - the queue the bot fills. Each line is `- [ ] date time | kind | summary` plus, only when the bot saved the item somewhere, a trailing ` | -> where` link. An unchecked `- [ ]` is unprocessed; `- [x]` is already done.
3. Collect the unchecked items. Apply the timeframe filter if given (`today` = today's date; `week` = the last 7 days; `all` = every unchecked). If there are none, say "nothing to catch up on" and stop.
4. Show the user a tight list, grouped by age (**Today** / **This week** / **Older**): time, kind, summary, and the `[[link]]` to where it landed (when present). Flag stale ones explicitly (e.g. "captured 9 days ago - still relevant?"), since a capture that mattered on a walk may be dead now.
5. Process the items WITH the user (this is a together-review, never an autonomous sweep). For each item - or a sensible batch - open the linked note/entry (or work from the queue summary when there is no link), read the actual captured content, and propose one of:
   - **Integrate** - fold it into the right existing or new note (person / project / concept / decision), following `references/ai-first-rules.md`: update existing notes, fill and link, reconcile contradictions - exactly as `/obsidian-save` would. Prefer updating an existing note over creating a near-duplicate.
   - **Keep as-is** - it is already filed fine (e.g. a daily-note thought); just acknowledge it.
   - **Discard** - stale or junk; remove the stray entry from where it landed.
   Surface your proposal and let the user confirm or redirect before you write anything.
6. After an item is handled, check it off in `catchup.md`: change its `- [ ]` to `- [x]` and append ` (processed YYYY-MM-DD)`. Never delete queue history - it is the record of what came in.
7. End with a one-line summary: N integrated, M discarded, K left unprocessed.

The split this enforces: the phone is for fast, dumb capture; the laptop is where you think and integrate. Same brain, two speeds - not two silos.

---

**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.

**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.

© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set51

The whole set →
obsidian-world obsidian-world is a Claude Code command that loads context from an Obsidian vault in stages. It runs on requests to catch up or check current priorities. CX Codex +1 ★ 5,412repo stars obsidian-decide obsidian-decide — a Claude Code command that extracts decisions from a conversation and files them in Obsidian, as dated lines or, with --formal, as a full ADR. CX Codex +1 ★ 5,412repo stars obsidian-save obsidian-save extracts decisions, tasks, ideas, and contacts from a Claude Code session directly into an Obsidian vault. Useful for archiving working context without manual note-taking. CX Codex +1 ★ 5,412repo stars obsidian-learn The obsidian-learn command reviews lessons in an Obsidian vault, marks stale or replaced findings, and surfaces repeated patterns for _CLAUDE.md. CX Codex +1 ★ 5,412repo stars obsidian-retrieval-eval obsidian-retrieval-eval evaluates Obsidian vault search quality using recall@k and MRR metrics. It tests search ranking against natural-language questions before changing indexing. CX Codex +1 ★ 5,412repo stars obsidian-projects obsidian-projects is a Claude Code command that builds project status from Obsidian notes, Git, and local docs. Ask for an overview or name one project to inspect. CX Codex +1 ★ 5,412repo stars obsidian-brainstorm obsidian-brainstorm is a Claude Code command that interviews you about an idea one question at a time, then writes a design note with alternatives and a recommendation. CX Codex +1 ★ 5,412repo stars podcast Extracts podcast episode metadata, transcript, and structured summary directly into an Obsidian vault note. CX Codex +1 ★ 5,412repo stars

More in the catalog

Project sponsors

Companies that keep this analytics open