The 24/7 Claude Code Personal Agent: Soul.md + Obsidian Vault + MCP + Dispatch Mode

Four-piece setup that turns Claude Code from a coding assistant into a personal agent that runs 24/7: a soul.md file that encodes your voice, an Obsidian vault that serves as living memory, MCP connections to Gmail/Notion/Calendar, and dispatch mode for phone control.

The Four Pieces

1. `soul.md` — Your Voice, Permanently

A plain-English markdown file that teaches Claude exactly how you speak and sound. It captures:

Writing style and tone
Communication preferences
How you want to be treated
Recurring patterns in how you give instructions

The payoff: you never re-explain your style again. Every new conversation starts with Claude already knowing your voice. Think of it as a persistent system prompt that lives in your project, not in a settings page.

2. Obsidian Vault — Living Memory

A private Obsidian wiki that changes and evolves over time. Stores:

Goals (quarterly, annual)
Active projects and their status
Interaction logs and decisions
Reference material Claude might need

Claude reads from the vault at the start of each conversation and pulls exactly what's relevant. The vault grows as you work — new projects get pages, completed ones get archived, decisions get logged.

This is the difference between an assistant with amnesia and one with a journal.

3. MCP Connections — Gmail, Notion, Calendar

Connect Claude to your actual work tools via MCP:

Gmail — read emails, draft responses
Notion — access workspace, read/update docs
Calendar — see schedule, understand availability

The advice: start with read-only access. Let Claude observe your tools before you give it write access. Build trust incrementally.

4. Dispatch Mode — Phone Control

Control the entire setup from your phone. Send instructions from mobile, Claude executes on your computer. The agent works while you're away from the desk.

This closes the loop: the agent has your voice (soul.md), your memory (vault), your tools (MCP), and your instructions (dispatch) — and none of it requires you to be at a keyboard.

How the Pieces Fit Together

[Phone — Dispatch Mode]
    ↓ instructions
[Claude Code]
    ├── reads soul.md → knows your voice
    ├── reads Obsidian vault → knows your context
    ├── connects via MCP → accesses your tools
    └── executes tasks autonomously

Each piece solves a different problem:

Piece	Problem it solves
soul.md	"Claude doesn't sound like me"
Obsidian vault	"Claude doesn't remember my projects"
MCP connections	"Claude can't access my tools"
Dispatch mode	"I have to be at my computer"

Implementation Order

If you're starting from zero:

soul.md first — write 20-30 lines about how you communicate. Biggest immediate payoff.
Obsidian vault second — start with one page per active project. Let it grow organically.
MCP third — connect Gmail read-only first. Add Notion and Calendar as you get comfortable.
Dispatch mode last — only useful once the other three are in place.

Key Takeaways

soul.md encodes your voice so you never re-explain your style
Obsidian vault gives Claude persistent, evolving memory across sessions
MCP connections (Gmail, Notion, Calendar) let Claude use your actual work tools — start read-only
Dispatch mode lets you control everything from your phone
Build incrementally: voice → memory → tools → mobile control

Resources

Claude Code — The agent runtime
Obsidian — The vault/wiki tool
Model Context Protocol (MCP) — The standard for connecting Claude to external tools
Maven — @maven_hq's platform