Drive coding work from Obsidian into Claude Code

They used Obsidian to draft plans, generate handoff notes, and launch Claude Code sessions, while an Efforts page kept each project’s status visible.

Done with Claude CodeClaude· Advanced· Nov 2026

What they did
They set up Claude Code in isolated Linux accounts on Arch, with a separate Obsidian vault for each major project. A QuickAdd action produced a plan prompt, then a workflow skill turned that into a plan note and a handoff document saved as subpages. A “Send to Claude Session” command then opened a tmux window tied to that plan so work stayed organized by task.
How it went
The setup created one session per plan and a shared Efforts page showing open PRs, completion percentage, the next step, and a color-coded state such as executing, idle, or closed. No run times or measured gains were reported.
Tips
Use one vault and one shell environment per project if you want the tracking to stay clean. Add an approval pause before anything that could change remote state, like pushing code or opening a PR.

Try it yourself with Claude Code

At [vault path], help me manage [task] in [repo path]. Make a plan note first, then create a handoff page that spells out the steps, the likely file changes, and how I should check the work. After that, open a tmux session for this plan and keep an Efforts page current with status, open PR links, percent complete, and the next action. Before any irreversible step, including pushing code, opening a pull request, submitting, deleting, or sending anything, stop and ask me to approve it.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.