Conversation interface
Nathan talks to Mercury through a direct command channel, using natural language to ask for research, summaries, files, job materials, troubleshooting, and operational decisions.
Private AI operations system
A real working AI operating layer, not a chatbot demo.
Mercury is Nathan's OpenClaw-based assistant system for coordinating communication, project memory, job applications, client follow-up, document search, web research, website operations, CMUX / Pi-assisted implementation workflows, and approval-gated automation from one conversational interface.
Architecture
The system runs as an OpenClaw agent layer. It combines messaging, tool access, working memory, browser-assisted research, CMUX / Pi-supported implementation loops, document workflows, website operations, job-search packaging, and explicit approval rules for sensitive or outward-facing actions.
Nathan talks to Mercury through a direct command channel, using natural language to ask for research, summaries, files, job materials, troubleshooting, and operational decisions.
Project files, daily notes, long-term memory, workflow docs, and task registers keep context available across sessions without relying on a single prompt.
Mercury can inspect local files, check websites, summarize emails when authorized, prepare documents, manage staged website updates, coordinate CMUX / Pi-assisted implementation passes, and run specialized workflows.
Email sends, public website changes, sensitive files, financial actions, credentials, and irreversible operations require Nathan's explicit approval before execution.
What Nathan Uses It For
Monitor leads, score fit, prepare tailored resumes and cover letters, draft custom application answers, and stop for CAPTCHA, legal, or unsupported-claim boundaries.
Design assistant workflows around real business records, Airtable/CRM-style structures, Zoho-style databases, documents, follow-ups, approvals, and operational handoff.
Build named OpenClaw agents such as Clyde for CRG Installations, connecting websites, email workflows, company databases, workspace tools, and daily operating routines.
Audit and stage updates for NathanBatiste.com, FlightBond Media, and other project sites while preserving working production configs and using CMUX / Pi-style implementation loops where useful.
Organize video ideas, AI-assisted content workflows, Vimeo portfolio links, project proof pages, messaging, and delivery plans.
Search, summarize, compare, and turn scattered information into next actions, drafts, checklists, and decision-ready notes.
Automate small, reversible, or read-only work by default while keeping sensitive actions behind explicit human confirmation.
Operating Pattern
A job application, site update, client workflow, research question, or operational problem starts as a plain-language request.
It reads the relevant local files, checks live sites, searches context, compares constraints, and identifies blockers before acting.
Drafts, resumes, website changes, diagrams, notes, links, or implementation plans are created around the actual workflow.
Mercury stops before public, irreversible, financial, credential, or outbound actions and asks Nathan to confirm.
Technical Details
Build Something Similar