Claude Code VPS Overview

Claude Code VPS — Overview & Getting Started

This document is the starting point. It explains what has been set up, why, and how both Patrick and Asia use it day to day. For the full technical setup log, see Claude-Code-VPS-Setup.

---

What this is

We run Claude Code — Anthropic’s AI coding and task agent — on a private Linux server (VPS). Both Patrick and Asia have their own separate accounts on that server, each connected to their own Claude.ai subscription (Patrick on Max, Asia on Pro).

This means we can:

• Run AI tasks on a server that’s always on, rather than on our personal computers
• Access those tasks from anywhere — terminal, phone, or Slack
• Share the same project files and Git repositories without conflicts
• Automate recurring tasks via Slack without being at a computer

No API keys, no per-task billing. Everything runs through our existing Claude subscriptions.

---

The two servers

Server	What it does
Claude Code VPS (46.224.129.16)	Where Claude Code runs. Patrick and Asia both have accounts here. This is the “brain.”
Agents VPS (167.235.236.99)	Where n8n runs. This receives Slack messages and passes tasks to the Claude Code VPS. This is the “messenger.”

You only ever SSH into the Claude Code VPS directly. The Agents VPS runs quietly in the background.

---

Three ways to access Claude Code

1. Terminal (SSH) — full interactive sessions

The most capable mode. Open a terminal on your Mac and connect:

ssh asia@46.224.129.16

Once connected, attach to your tmux session (a persistent workspace that stays alive even when you close your laptop):

tmux attach -t asia-kb      # knowledge base work
tmux attach -t asia-agents  # general agent tasks

Then start Claude Code:

cd /srv/baseworks/knowledge-base
claude

You now have a full, interactive Claude Code session. Talk to it like you would in the Claude.ai chat — ask questions, give it tasks, have a back-and-forth conversation. It has access to all the shared Baseworks files on the server.

When you’re done, detach from tmux without closing the session:

Ctrl+B then D

The session keeps running on the server. Come back any time and pick up where you left off.

---

2. Remote Control — phone or browser (Patrick only for now, Asia coming soon)

If Patrick has a tmux session running with Claude Code open, he can continue it from his phone or any browser without touching a terminal.

Inside Claude Code, run:

/remote-control

This generates a URL and QR code. Open either on your phone or any browser — you’re now in the same session, with full context, having a real back-and-forth conversation. Not one-shot commands — a full chat.

The tmux session on the VPS keeps the process alive, so it works even after you close your laptop.

Asia: Remote Control is currently Max plan only. Pro plan support is listed as coming soon from Anthropic. Until then, use Slack for away-from-terminal access (see below).

---

3. Slack (or Discord) — tasks and commands from anywhere

Send a message to the right Slack channel. n8n picks it up, passes it to Claude Code on the VPS, and posts the result back. This works from your phone, no terminal needed.

This is best for:

• Triggering tasks (“scan the WordPress plugins for updates”)
• Infrastructure commands (“show running containers”, “stop OpenClaw”)
• Filing notes to the knowledge base
• Checking status of anything on the server

Each message is a self-contained task — Claude Code runs it and reports back. For back-and-forth conversations, use the terminal or Remote Control.

Relevant Slack channels:

Channel	Use for
#agent-alerts	Infrastructure commands, kill switch, server control
#vault-inbox	Filing notes and captures to the knowledge base
#wordpress-updates	WordPress and site-related tasks
#content-strategy	Content-related agent tasks
#forum-responses	Forum and community responses

---

Asia’s getting-started checklist

These steps happen after Patrick has completed the server setup (Phases 1–9 in Claude-Code-VPS-Setup).

• Get your SSH public key to Patrick so he can add it to the server
• SSH into the server for the first time: ssh asia@46.224.129.16
• Run claude — follow the login prompt to authenticate with your Claude.ai Pro account
• Paste the login URL into your browser, log in, done — credentials are saved permanently
• Create your tmux sessions: tmux new -s asia-kb and tmux new -s asia-agents
• Add MCP servers (run these in your shell, not as root):

  claude mcp add --transport http github https://api.githubcopilot.com/mcp/
  claude mcp add --transport stdio filesystem -- npx -y @modelcontextprotocol/server-filesystem /srv/baseworks

• Test: cd /srv/baseworks/knowledge-base && claude — ask it “what is this project?”

---

Shared project files

Both Patrick and Asia work from the same directories on the server:

Path	Contents
/srv/baseworks/knowledge-base/	Obsidian vault (baseworks-kb-shared-brain)
/srv/baseworks/changelog/	Baseworks site changelog (baseworks-changelog)
/srv/baseworks/CLAUDE.md	Project config Claude reads automatically

Always git pull before making changes. Claude Code does this automatically if you ask it to.

---

How access works by scenario

Where you are	What to use
At desk, Mac	SSH + tmux → full interactive Claude Code session
Away from desk, Patrick (phone/browser)	Remote Control link from an active tmux session
Away from desk, Asia (phone)	Slack message → n8n → Claude Code → result posted back
Scheduled or automated tasks	Slack/n8n → claude -p runs automatically

---

What Claude Code can do from Slack (examples)

These are sent as plain messages to the appropriate channel:

• “Scan all WordPress plugins for available updates and write a report to the vault”
• “Take a database backup before we make any changes”
• “File this note in the knowledge base: [paste content]”
• “Show me what’s running on the server”
• “Stop OpenClaw and disable its nginx proxy”
• “Check the firewall rules”
• “Summarise today’s vault activity”

Claude Code works through the task, then posts a result back to the channel.

---

OpenClaw note

OpenClaw (a previous AI agent platform we were testing) is still installed on the Claude Code VPS but kept stopped. It is preserved in case we want to evaluate it again later, but it is not part of the current workflow. You do not need to interact with it. If it ever needs to be restarted, Patrick handles that. See OpenClaw-Deployment-Guide for reference.

---

Related docs

• Claude-Code-VPS-Setup — full technical setup log (Phases 1–11)
• Deployment-Log — chronological record of all infrastructure sessions
• OpenClaw-Deployment-Guide — OpenClaw reference (archived use)