How I run my work life on Stacklist as my operating system
Stacklist as Personal OS — Writer KT (v2, corrected)
Kyle Hudson, CEO of Stacks Inc., runs his entire personal and professional operating system—daily briefs, meeting notes, strategy, and team coordination—inside Stacklist via MCP, with two Claude instances (a Mac Mini M4 and a MacBook Pro) sharing state through the product's API rather than local filesystems. The piece details his specific workflow architecture, team roster, the system's naming history (KOS → Rue → Virgil), the Stacklist schema of stacks/cards/tags, and how dogfooding his own SaaS turns every personal workflow bug into a CEO-level product decision.
[DRAFT] Substack — Virgil
Virgil is a personal operating system built by a CEO who wires together Slack, Gmail, Calendar, Granola, Todoist, and other tools through AI and an MCP server into a single daily briefing card inside Stacklist—the SaaS product his own company sells to local expertise businesses. The piece details the daily ritual of handoff cards, overnight automated triage, and an advisory layer that loads the author's known behavioral patterns to coach him away from tendencies like over-solving, conflict avoidance, and hyperfocus rabbit holes.
[SUPERSEDED v1] dev.to — Markdown as a syscall (replaced by v2)
# Markdown as a syscall: how I run my life on MCP and my own SaaS [[IMAGE_SLOT:cover — simple diagram of two machines writing to one shared state layer, labeled Stacklist]] For about a month, neither of my two machines has been the source of truth for my life. Stacklist is. Stacklist is the SaaS my company ships. It's a hub — a social curation network where people and businesses build organized, browsable collections of links, notes, and Markdown. We sell it to local expertise businesses. I also happen to run my entire operating system on top of it. The closest pop-culture analog is *wake up, Jarvis*. Minus the suit. Plus a lot less drama. In practice, "Jarvis" is eight different tools I used to juggle by hand: Slack, Gmail, Google Calendar, Granola meeting notes, the full archive of every meeting I've had, Todoist, Lightfield CRM, Linear. Every morning Virgil pulls from all of them, cleans, sanitizes, prioritizes, and surfaces only what I've pre-authorized to reach me
[SUPERSEDED v2] dev.to — (replaced by v3)
The piece details a founder's system for consolidating inputs from Slack, Gmail, Calendar, and other tools into a single Markdown-based hub (Stacklist) using two machines—an always-on Mac Mini and an interactive MacBook—that share state exclusively through MCP tool calls rather than local filesystems. It explains the architectural choices: naming-convention-based schemas instead of databases, AI as a first-class API client rather than a bolt-on, and scheduled Claude Code jobs that produce daily briefs, weekly syntheses, and monthly rollups without human intervention.
[SUPERSEDED v3] dev.to — (replaced by v4)
A founder describes building "Virgil," a Claude Code-based personal operating system that uses MCP servers to read from eight input sources—Slack, Gmail, Calendar, Granola, Linear, Lightfield, Texts, and WhatsApp—and distills everything into a single daily Markdown card written to Stacklist, the SaaS product his own company ships. The setup inverts typical AI-plus-notes architectures by making the AI a first-class API client rather than a bolt-on, following a strict rule that all working state flows through Stacklist via MCP, producing a morning standup card with a focus list, overnight digest, and prioritized action plan before the founder even opens a browser tab.
[DRAFT v4] dev.to — How I run my life on Markdown, MCP, and the startup we're building
A founder describes building "Virgil," a Claude Code orchestrator that pulls context from eight input sources—Slack, Gmail, Calendar, Granola, Linear, Lightfield, Texts, and WhatsApp—via MCP servers and distills everything into daily and weekly Markdown cards stored in Stacklist, the startup they're building as a central knowledge hub. The setup follows a strict rule that all working state lives in Stacklist, making it a single canonical source that any AI client (Claude Code, Claude desktop, or Stacklist's own AI) can query consistently, inverting the typical pattern where AI is bolted onto human-first tools.
This page discusses how the author utilizes Markdown and the Stacklist MCP to manage their life amidst overwhelming inputs like Slack, Gmail, and calendar invites. It highlights productivity tools and techniques that can help streamline daily tasks.