Skip to main content

​
Use cases & user stories

Real-world examples of what people do with Headmaster, organized by category.

​
Dev workflow

The Headmaster (orchestrator) breaks a plan into phases, The Builder implements each phase, and a QA specialist tests. Plan → implement → test → fail → repair → ship. The whole loop runs in Run It Yourself mode with the Council for architecture decisions.
A specialist reviews git diffs before committing — flagging debug prints, hardcoded secrets, bare except clauses, and unresolved TODOs. Run it as a pre-commit hook or from the chat before pushing.
A specialist watches agent-to-agent workflows, catches where they break, and fixes them live. Run it in a side conversation while the main workflow runs in another.
Run multiple Headmaster instances in parallel — each in its own project folder, each with a different model, each working on a different part of the codebase. Sessions don’t interfere.
When a workflow is stable, compile the skill instructions into a Python script. Only involve the LLM at necessary steps. Improves reliability and consistency for production workflows.

​
Personal assistant

“Every weekday at 9am, summarize my inbox and post the summary to Telegram.” The agent writes the schedule, registers it in The Schedule, and runs it in Autopilot. You wake up to a Telegram message with your inbox summary.
“Google me and ship a landing page.” The agent runs the searches, creates the page, SSH’s into your VPS, uploads the page, and texts you when it’s done.
“I want you to use Obsidian to manage my tasks and cross-check with my Apple Calendar.” The agent reads and writes to Obsidian vaults and queries Apple Calendar for conflicts.
Set up Headmaster for your family on WhatsApp. Three members share the same agent — it reminds people of birthdays, tracks shared shopping lists, and answers questions.
Tier 1 is a pure Python script (no LLM) that detects new email and manages state. Tier 2 is the LLM session — only invoked when new email arrives. Zero LLM calls when the inbox is idle.

​
Integrations

Connect Headmaster to your Postgres database via MCP. Ask questions in plain English — the agent writes and runs the SQL, then formats the result as a table.
Connect to GitHub via MCP. The agent reads issues, creates branches, writes code, opens PRs, and responds to review comments — all from the chat.
Connect to Google Calendar. The agent reads your schedule, finds free slots, and creates events. “Schedule a 30-minute meeting with John next Tuesday afternoon” — it handles the whole flow.
Connect to Slack via MCP. The agent reads channel messages, responds to mentions, and posts summaries. Run in Autopilot to get daily channel digests.

​
Creative

Give The Writer a one-paragraph brief and get a 10-slide deck. Iterate on the design with The Storyteller for motion and visual narrative.
The Wordsmith writes serial fiction. Give it a premise and a character bible — it writes chapters, maintains continuity across sessions via memory, and tracks plot threads.
The Designer generates logo concepts. Iterate on style, color, and composition. Export as SVG for production.

​
Business ops

Every Friday at 5pm, the agent pulls data from your database, generates a Word report, and emails it to the team. Runs in Autopilot.
The agent reads invoice PDFs from a folder, extracts the relevant data, and writes it to a spreadsheet. Batch-processes 50 invoices in one run.
The agent reads incoming support emails, classifies them by urgency and topic, drafts responses, and posts them to a Slack channel for approval.
The agent reads a meeting transcript, writes structured notes, creates action items, and posts them to your project management tool.

​
Research & content

The Researcher reads 20 papers on a topic, synthesizes the key findings, identifies gaps, and writes a structured literature review with citations.
The agent researches 10 competitors, compares their features and pricing, and generates a comparison spreadsheet and summary report.
Give the agent a topic and a set of sources. It reads the sources, writes a blog post, and generates a cover image.
Every Monday, the agent reads your team’s activity from the past week and writes a newsletter. Posts it to your email list via the email integration.

​
Enterprise

The agent writes code, runs tests, and prepares a deployment. Every step requires human approval. The full audit trail is stored in the session transcript.
Multiple users connect to the same remote runtime. They share memory, skills, and integrations. Each user has their own conversation history.
Every agent action — file access, tool call, approval, denial — is logged with a timestamp. Export the logs for compliance reviews.
The agent logs token usage per conversation and per task. View cost breakdowns in the runtime dashboard. Set cost limits per task to prevent runaway spending.

​
Privacy & self-hosted

Run Headmaster on a machine with no internet. Use local models only. No data leaves the machine. File operations, code execution, and document generation all work offline.
Run the runtime on your own server. Connect to it from the desktop app on your laptop. Your data never touches a machine you don’t control.
Headmaster does not phone home. No usage analytics, no crash reports (unless you explicitly send a bug report). The app doesn’t make outbound connections except to your configured model providers.

The Schedule

Automate recurring use cases on a cron schedule.

Specialists

Pick the right specialist for your use case.