The complete guide to your own AI infrastructure

How to get the most from this guide

This guide is designed to be used alongside an AI assistant. Here's the workflow:

1. Read a section on this page.
2. Find the copy-to-clipboard code blocks and prompts (blue-bordered sections).
3. Paste them directly into Claude, ChatGPT, or your preferred AI.
4. Follow the AI's instructions step by step.
5. Move to the next section.

The AI will guide you through terminal commands, configuration changes, and troubleshooting. You're never alone in this process.

What you'll accomplish

• Set up a Mac Mini as a dedicated 24/7 AI server on your home network.
• Create a context file system that travels with you across any AI platform.
• Access your AI infrastructure from any device (laptop, phone, tablet) using SSH and VPN.
• Run Claude Code, OpenClaw, Cursor, and other AI tools on headless hardware.
• Never lose your AI knowledge again — it's yours, not locked in a platform.

Estimated timeline

Budget 2–4 hours for the full setup. You can do it in one weekend.

What you need to start

• A Mac Mini (M1, M2, M3, M4, or M4 Pro).
• An Ethernet cable (Cat6a or Cat8 recommended).
• A laptop, desktop, or phone for remote access.
• A Cloudflare or similar DNS provider (free).
• A Claude, ChatGPT, or Gemini subscription to follow along.

The problem with how we use AI today

When you open ChatGPT or Claude in the browser, you start a chat that lives in a silo:

• The AI doesn't know you — your projects, preferences, goals, or history.
• Your conversations are saved, but locked inside each platform. Switch services and that context stays behind.
• You're limited to the interface and capabilities of one platform.
• Most importantly: as AI moves from chat to agents, traditional chat conversations become obsolete. The future is agentic workflows, not chat history.

Every conversation is isolated. Chat platforms don't talk to each other. And chat itself is becoming outdated as AI moves toward agents.

The better way: AI with memory

What if every AI assistant you used already had a complete briefing about you?

That's what this guide builds. A context file system — your personal knowledge base. It contains:

• Who you are (background, skills, values).
• How you work (preferences, communication style, decision rules).
• What you're building (project summaries, tech stack, known decisions).
• What you've learned (past solutions, mistakes to avoid, patterns that work).

Every time you start a new session with an AI, you paste in your context file. The AI reads it and understands you immediately. No ramp-up time. No explaining yourself.

Infrastructure: the real advantage

• Ownership. Your AI infrastructure is yours. No vendor lock-in. Switch between Claude, ChatGPT, or Gemini whenever you want.
• Flexibility. Run any AI tool, any time. Pick the best tool for the job.
• Always-on automation. Your Mac Mini runs 24/7. AI agents keep working while you sleep.
• No subscription per tool. Claude Max ($200/mo) covers Claude Code, Cowork, and Claude API — most needs in one bill.

The economics

Let's be concrete. What does this cost?

The question to ask yourself

"What would I pay for a personal assistant who works 24/7, never sleeps, and gets smarter every week?"

$200–250/month is less than you'd pay a part-time human assistant for 10 hours/week. And this one never gets tired or makes mistakes from fatigue.

The AI landscape right now

As of early 2026, three major AI providers dominate:

• Claude (Anthropic) — best for coding, writing, reasoning, and long-form thinking.
• ChatGPT (OpenAI) — most popular, broadest ecosystem, best for general use.
• Gemini (Google) — great Google integration, best for productivity workflows.

This guide recommends Claude as your primary because it excels at the tasks in this guide (coding, terminal work, context understanding). But the infrastructure we'll build works with any AI provider. The landscape changes fast — what matters is building AI infrastructure that's platform-independent.

Chat vs agents — the shift happening now

Most people use AI as chat: you ask a question, get an answer, done. Agentic AI is fundamentally different.

An agent doesn't just answer questions. It takes actions: writing files, running commands, managing projects, reading your entire codebase, executing workflows.

• Claude Code — reads your entire codebase, makes edits, runs git, refactors code.
• Claude Cowork — creates files, runs code, manages projects.
• OpenClaw — runs 24/7 as a background service, responds to messages, executes workflows.

Chat is the training wheels. Agents are the real thing. This guide is about agents, not chat.

How AI is charged: two models

There are two ways to pay for AI:

Flat-rate subscriptions: Claude Pro ($20/mo), Claude Max ($100–200/mo), ChatGPT Plus ($20/mo). You pay monthly and use as much as you want (within reasonable limits). Perfect for individuals and small teams.

Usage-based (API): pay per token (input + output). Anthropic API costs ~$0.003 per 1K tokens. Cheap per message, but adds up quickly if you're running automated agents 24/7.

The sweet spot for this guide: Claude Max ($200/mo flat) for Claude Code + Cowork, paired with OpenClaw using the API ($5–30/mo). Total: ~$225–250/mo for your own AI infrastructure.

What this guide's stack costs

• Mac Mini M4: $599–999 one-time.
• Claude Max: $200/mo.
• OpenClaw API usage: $5–30/mo.
• Cursor (optional): $20/mo.
• Everything else: free (VS Code, Tailscale, Homebrew).

Total ongoing: ~$225–250/mo for a world-class AI infrastructure that's 100% yours.

The Mac Mini

The Mac Mini is the heart of your AI infrastructure. Choose based on your budget and use case:

• Mac Mini M4 (base) — $599. 10-core CPU, 10-core GPU, 16GB RAM, 256GB SSD. Enough to start.
• Mac Mini M4 (recommended) — $799. 16GB RAM, 512GB SSD. Sweet spot for most users.
• Mac Mini M4 (ideal) — $999. 24GB RAM, 512GB SSD. Future-proof, handles heavy workloads.
• Mac Mini M4 Pro — $1,399+. Overkill for this guide, but future-proof for scaling.

Apple Silicon (M1–M4) chips are crucial. They're efficient enough to run 24/7 without overheating and are purpose-built for machine learning. Older Intel Mac Minis will overheat.

Networking

Get your Mac Mini on Ethernet (hardwired) instead of Wi-Fi. It's faster and more reliable.

• Ethernet cable (Cat6a or Cat8): $10–20. Amazon link: Cat8 Ethernet Cable.
• Your existing router or mesh system works fine. No special networking needed.

What you already have

• A laptop, phone, or tablet for remote access (any OS works).
• An internet connection.
• A keyboard and monitor for initial setup only — you can borrow one. You won't need it after setup.

What you don't need

• A dedicated monitor (it runs headless).
• A dedicated room or server rack.
• Any Linux or Windows knowledge.
• A computer science degree.

Our recommended setup

• Mac Mini M4 (24GB/512GB): $999.
• Cat8 Ethernet cable: $15.
• TP-Link Deco mesh router (most likely already owned): search Amazon.

Total additional hardware investment: ~$1,014.

Initial setup (with monitor and keyboard)

Plug in a monitor, keyboard, ethernet cable, and power. Go through macOS setup:

• Sign in with your Apple ID.
• Set up Wi-Fi as a backup (you'll use Ethernet primarily).
• Create your admin account (e.g., your name).
• Complete the setup and get to the macOS desktop.

Configure for always-on operation

Your Mac Mini needs to stay awake and restart after power failures:

• System Settings → General → Energy: enable "Prevent automatic sleeping."
• Enable "Wake for network access."
• Enable "Start up automatically after power failure."

These settings ensure your AI infrastructure stays live 24/7 even if there's a power outage.

Set a static IP address

A static IP means your Mac Mini always has the same address on your network. That makes it reliable to connect to remotely.

• System Settings → Network → Ethernet → Details → TCP/IP.
• Configure IPv4: select "Manually."
• IP Address: choose one outside your router's DHCP range (e.g., 192.168.1.100 or 192.168.68.82).
• Subnet Mask: 255.255.255.0 (or your network's mask).
• Router: your router's IP (e.g., 192.168.1.1 or 192.168.68.1).
• DNS: 1.1.1.1, 8.8.8.8 (Cloudflare and Google).

I'm setting up a static IP on my Mac Mini. My router is at [YOUR ROUTER IP]. Help me choose an IP address that won't conflict with DHCP and guide me through configuring the network settings.

Enable remote access

• System Settings → General → Sharing: enable "Remote Login."
• Remote Login = SSH (lets you control the Mac Mini from a terminal).
• Enable "Screen Sharing" so you can see the macOS desktop remotely.

Note your computer name (e.g., "Blakes-Mac-mini") and static IP for the next step.

Auto-login (optional for headless)

• System Settings → General → Users & Groups.
• Select "Automatic Login."
• Choose your admin account.

Trade-off: auto-login adds convenience (restarts are instant) but requires FileVault to be OFF. For maximum security, skip auto-login and accept you'll need to enter your password after a restart (rare, since we prevent sleeping). Both approaches are valid.

Verify it works

Before unplugging the monitor, test from another device on the same network:

ssh yourusername@192.168.x.x

If this connects to a terminal, SSH works.

For Screen Sharing: open Finder → Go → Connect to Server → vnc://192.168.x.x. If both work, you're ready to unplug the monitor and go headless.

Unplug the monitor

Once SSH and Screen Sharing are working, disconnect the monitor and keyboard. Your Mac Mini is now headless. Everything from here is done remotely.

SSH (terminal access)

SSH = Secure Shell. It gives you a text-based terminal into your Mac Mini. You type commands as if you're sitting at the Mac Mini.

ssh yourusername@192.168.x.x

SSH clients for different devices:

• Mac/Linux: built-in Terminal app.
• iPhone/iPad: Termius (free) or other SSH apps.
• Windows: Windows Terminal or PuTTY.

Screen Sharing (desktop access)

• Mac: Finder → Go → Connect to Server → vnc://192.168.x.x.
• iPhone/iPad: Screens 5 (~$25 one-time) or other VNC apps.
• Windows: any VNC client (RealVNC, TightVNC, etc.).

Screen Sharing uses more bandwidth than SSH. SSH is faster for most tasks.

Tailscale VPN (access from anywhere)

Problem: SSH and Screen Sharing only work when you're on your home network. What if you want to access your Mac Mini from a coffee shop, hotel, or a different office?

Solution: Tailscale creates an encrypted tunnel between your devices. Free for personal use (up to 100 devices).

Install on Mac Mini:

brew install --cask tailscale

Then download and install Tailscale on your phone, laptop, and tablet from tailscale.com. Sign in with the same account on all devices. Each device gets a unique Tailscale IP (100.x.x.x) that works from anywhere.

# Access from anywhere (via Tailscale)
ssh yourusername@100.x.x.x
vnc://100.x.x.x

When to use what

Quick reference

# Local network (at home)
ssh yourusername@192.168.x.x
vnc://192.168.x.x

# Remote access (anywhere via Tailscale)
ssh yourusername@100.x.x.x
vnc://100.x.x.x

Prerequisites: Homebrew and Node.js

Before you install any AI tools, you need Homebrew (macOS package manager) and Node.js (JavaScript runtime). If you already have these, skip ahead.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

brew install node

brew --version && node --version && npm --version

Claude Code

Claude Code is a command-line AI coding agent. It understands your entire codebase, runs git commands, and can read/write/refactor code in Terminal. If you have Claude Max, it's included — no extra cost.

npm install -g @anthropic-ai/claude-code

cd /path/to/your/project && claude code

OpenClaw: the game changer

OpenClaw is a self-hosted AI agent gateway. Unlike chat platforms, OpenClaw runs 24/7 as a background service. You text it, email it, or message it on Discord — and your AI assistant responds from your own infrastructure.

Path A — quick setup (your main account)

Simpler, all in one place. Good for learning.

npm install -g openclaw@latest
openclaw onboard --install-daemon

The setup wizard will ask:

• Gateway location → local (runs on your Mac Mini).
• Bind address → loopback (127.0.0.1 — only accessible from your Mac Mini or via VPN).
• Auth token → generate a strong token (OpenClaw will create one — save it).
• Messaging channel → connect Discord or Telegram so you can text your agent.

Path B — security-first (dedicated user account)

More isolated. OpenClaw runs as its own Standard user account, not your admin account. Recommended for production use.

• System Settings → Users & Groups → + → account type Standard (NOT Admin) → name openclaw-agent.
• Create the account and set a strong password.

su - openclaw-agent

Then run the OpenClaw installation in that account's shell. The setup isolates OpenClaw from your main admin account — if there's ever a security issue, it's contained.

Which path? If this is your first time, start with Path A. Once you're comfortable, upgrade to Path B by re-running the installer in the dedicated account.

VS Code and Cursor

VS Code is the free industry-standard code editor. Cursor is VS Code with AI deeply built in — same editor, but with AI autocompletion, code generation, and agentic workflows built natively. Both optional, both recommended if you write code.

brew install --cask visual-studio-code

brew install --cask cursor

Quick reference

Next step

Your infrastructure is now installed. The real magic happens in Section 8 — your context file system. This is what separates a powerful AI tool from a world-changing one.

Why context files matter

Think about how you use AI today. Every conversation starts from zero.

• You have to re-explain who you are and what you do.
• You have to re-explain your tech stack and preferences.
• You have to re-explain past decisions and why you made them.
• If you switch to a different AI platform, you lose all that context and start over.

This is inefficient. And it doesn't scale when you're using multiple AI tools simultaneously.

A context file solves this. It's a single document that travels with you across all AI platforms and tools.

Your master context file

Start with one master context file called CLAUDE.md in your Mac Mini home folder. This is your personal briefing document.

It should include:

• Your name, location, email, phone.
• Your professional background.
• Your values and working style.
• Your tools and subscriptions (Claude Max, Stripe account, GitHub, Vercel, etc.).
• Current projects (brief one-liner each).
• Recent decisions and why.
• Your AI philosophy.

To create your master context file, use this prompt:

I'm building my personal context file system. Interview me to create my master CLAUDE.md file.

Ask me questions about:
1. Who I am professionally (background, skills, what I'm known for)
2. How I prefer to work and communicate (direct vs collaborative, written vs verbal, timezone, working hours)
3. My values and principles (what's important to me, what I hate, what I love)
4. My tools and subscriptions (what AI platforms do I use, what SaaS do I pay for)
5. My current projects (what am I building, what's my tech stack, what's my biggest priority)
6. Past decisions and lessons learned (why I made certain technical choices, what worked, what didn't)
7. My AI philosophy (how I want AI to assist me, what I've learned about effective AI use)

After gathering all this, write it as a master CLAUDE.md file formatted in Markdown. Make it readable, organized, and something I can copy directly into my Mac Mini.

Interview me now — ask one question at a time, and wait for my answer before moving to the next question.

Save this file to your Mac Mini at ~/CLAUDE.md. You'll paste it into every AI session.

Project-level context files

Beyond your master context, create a separate CLAUDE.md file in each project folder.

# [Project Name] — Context File

## What This Is
[One-paragraph description of the project]

## Owner & Entity
- Owner: [Your name]
- Repository: [GitHub link]
- Domain: [domain.com]
- Deployment: [Vercel / Cloudflare Pages / custom]

## Tech Stack
- Frontend: [React / Next.js / HTML+CSS / etc.]
- Backend: [Node.js / Python / Serverless / etc.]
- Database: [Supabase / PostgreSQL / Firebase / etc.]
- Hosting: [Vercel / Cloudflare Pages / AWS / etc.]

## Key Decisions
- [Why you chose this tech]
- [Constraints or requirements you're working within]

## What's Been Done
- [ ] Task 1
- [x] Task 3 (completed)

## What's Left
- [ ] Priority 1
- [ ] Priority 2

## Design & Brand Direction
- [Color palette, typography, brand guidelines]

## Session Protocol
At the start of every session:
1. Read this file first
2. Summarize where the project stands

During the session:
- Update this file immediately with new decisions

At the end of the session:
- Write down what was accomplished and decided
- Provide git commands to commit and push

The session protocol

At the START of a session: open your master CLAUDE.md and the project CLAUDE.md, paste both into your AI session, and ask the AI to "Read my context files and summarize where I stand." The AI understands you immediately.

DURING the session: whenever you make a decision, ask the AI to "Update my context file with this decision." The AI updates the file in real time — decisions don't live only in chat.

At the END of a session: the AI summarizes what was accomplished, updates your context file one final time, and you commit and push the updated file to GitHub. Your context travels with you.

Getting started: your first context file

Right now, go create your master CLAUDE.md. Use the prompt above. Interview yourself. Save it to ~/CLAUDE.md on your Mac Mini.

From now on, every time you start an AI session, paste your context files first. This single practice will transform how you use AI.

Templates & examples

The Downloads page has ready-made templates for both master and project context files.

Why security matters here

Your AI server has access to your files, your code, and your business data. It's connected to the internet via messaging channels. A small effort now prevents big problems later.

The security checklist

• FileVault (full disk encryption):Apple menu → System Settings → Privacy & Security → Turn On. Encrypts your entire drive at rest. Trade-off: FileVault ON = max data protection if the Mac Mini is stolen, but breaks auto-login. OFF = headless convenience. Pick what fits.
• macOS Firewall: System Settings → Network → Firewall → On → Options → Block all incoming. No unsolicited connections reach your Mac Mini.
• Lulu outbound firewall: free, open-source app from Objective-See. Download from objective-see.org. Monitors what goes OUT of your Mac Mini.
• Disable sharing services: System Settings → General → Sharing. Turn OFF Screen Sharing, File Sharing, Remote Management when not needed. Only enable what you actually use.

The dedicated user account approach

The security-first approach: instead of running OpenClaw as your admin account, create a Standard user account called openclaw-agent. The AI only sees files in that user's home directory.

• System Settings → Users & Groups → +.
• Account type: Standard (NOT Admin).
• Full Name: openclaw-agent. Set a strong password.

Switch to that account and install OpenClaw there. The isolation is transparent — your agent works the same, but the security boundary is much tighter.

OpenClaw security configuration

After installation, OpenClaw creates a config file. Edit it to harden security:

{
  "gateway": {
    "bind": "127.0.0.1",
    "port": 18789,
    "authToken": "your-256-bit-token-here"
  },
  "tools": {
    "system": {
      "denyCommands": [
        "system.run",
        "system.exec",
        "canvas.eval",
        "shell.command"
      ]
    },
    "fs": {
      "workspaceOnly": true
    }
  },
  "messaging": {
    "discord": {
      "allowFrom": ["YOUR_USER_ID_HERE"]
    }
  }
}

• bind: 127.0.0.1 — loopback only. No external access.
• authToken — generate with openssl rand -hex 32. Required for every request.
• denyCommands — blocks dangerous operations. Your AI can still do productive work, just not system-level damage.
• workspaceOnly: true — files are sandboxed to the OpenClaw workspace folder.
• allowFrom — only your Discord user ID can trigger the bot.

Tailscale VPN for remote access

You've bound OpenClaw to loopback (127.0.0.1), which is secure but only works from the Mac Mini itself. To access it from your phone or laptop, use Tailscale (covered in Section 6). Your Mac Mini stays hidden from the internet but you can SSH from anywhere.

API key security

Your Claude API key is like a credit card for AI. Guard it carefully.

• Never commit API keys to git. If you do, immediately rotate the key at console.anthropic.com.
• Store in locked Apple Notes or a .env file with chmod 600. Both are encrypted locally. Never plaintext on your desktop.
• Set spending limits at console.anthropic.com. If your key leaks, Anthropic cuts off access once you hit your limit.
• Rotate keys monthly. Delete the old, generate a new one, update your config.

Credentials checklist

Message your AI from anywhere

OpenClaw runs on Discord, Telegram, Slack, or WhatsApp. Your AI responds instantly, 24/7, from your own infrastructure. Common use cases:

• Quick questions and brainstorming.
• Task lists and reminders.
• Status checks on ongoing projects.
• Code review and debugging help.
• Business intelligence and data analysis.

Daily briefings

Set up a scheduled task that runs every morning. Your AI summarizes your calendar, checks project status, and flags anything urgent.

Every morning at 7am, summarize:
- My calendar for today (any big meetings?)
- Active projects (status, blockers, what's due?)
- Urgent emails or Slack messages
- Any alerts from my business systems

Format as a 2-minute read. Flag anything that needs immediate attention.

Coding with AI

Claude Code understands your entire codebase. You're no longer copying code snippets into chat windows — your AI has context on everything.

cd /path/to/my/project && claude code

# Then in the interactive session:
"There's a bug in the authentication flow where users aren't being redirected after login.
Read the auth files and fix it."

# Claude Code reads your entire auth system, finds the bug, makes the fix, and commits to git.

Business automation

• Lead follow-up reminders: your AI checks a spreadsheet of leads, reminds you who to follow up with, sends draft emails (ALWAYS drafts, never auto-send).
• Invoice tracking: monitor unpaid invoices, send reminders, flag overdue payments.
• Social media drafts: 5 social media posts per week for your industry. You review and post manually.
• Competitive research: weekly summaries of what competitors are doing, pricing changes, new products.
• Financial monitoring: QuickBooks alerts, Stripe sales summaries, cash flow analysis.

Research & analysis

"Research the top 5 competitors in my space. For each, find:
- Their pricing model
- What problems they solve
- Their recent funding/news
- What they're missing that I can build

Summarize in a 1-page comparison table."

"Analyze this spreadsheet of sales data. Tell me:
- What stands out?
- Which customers are most valuable?
- What patterns do you see?
- What should I focus on next?"

Multi-channel setup

• Discord (personal): quick questions, brainstorming, task management.
• Telegram (business): client alerts, lead notifications, business metrics.
• Email: daily briefings, weekly reports, formal summaries.

Your next step

Pick ONE thing you want to automate. Write it down:

Now that my AI infrastructure is set up, here's what I want to automate first:
[Describe your first automation goal]

What should I do next? Break down the steps to make this work.

Podcasts & audio

Official documentation

• Claude: docs.anthropic.com — API reference, model capabilities, prompting.
• OpenClaw: docs.openclaw.ai — setup, security hardening, advanced config.
• Tailscale: tailscale.com/kb — VPN setup, remote access patterns.
• Cursor: docs.cursor.com — AI IDE features, keyboard shortcuts.

YouTube channels

• Fireship — tech explainers in 100 seconds. Quick context on any tool.
• NetworkChuck — networking fundamentals, Linux, hands-on labs.
• Matt Wolfe — weekly AI tools roundup. Discovery channel for new products and capabilities.

Communities

• r/LocalLLaMA (Reddit): local AI, self-hosted tools, privacy-first infrastructure.
• r/ClaudeAI (Reddit): Claude users sharing workflows and prompts.
• OpenClaw Discord: community, feature requests, troubleshooting.
• Anthropic Discord: Claude product discussions and developer announcements.

The AI landscape moves fast — new tools, new capabilities, new patterns every week. The key is staying curious and experimenting. Your infrastructure is designed to evolve with you.

OnyxCoded is the web development and AI infrastructure studio that built this guide. If you want hands-on support during setup, custom automation agents, or ongoing infrastructure management, head over to onyxcoded.com.

Our services

Contact OnyxCoded

• Email: info@onyxcoded.com
• Phone: (949) 750-5067 (text preferred)
• Web: onyxcoded.com

Feedback on this guide

Found something confusing or outdated? Email hello@goneckdeep.com. This guide is living documentation. As AI tools evolve, we update it. Your feedback helps us make it better for everyone.

You're done

Congratulations. You've gone neck deep into AI infrastructure. You now have:

• A 24/7 AI server running on your Mac Mini.
• Remote access from any device, anywhere.
• A context file system that travels with you.
• Always-on automation via OpenClaw.
• Professional development tools (Claude Code, Cursor, VS Code).
• Understanding of AI tools, pricing, and capabilities.

You're now in the top 5% of AI-efficient people. What you build from here is up to you.