Your first hall.

A practical introduction to the parts of Longhall, what you need, and where each tool’s boundaries sit.

Three parts, one workspace.

1. The hub serves the panel, connects your machines and keeps orders, routines and an audit log. It can live on your Mac or an always-on Linux server.
2. An agent on each machine connects the hub to local tools and sessions. Hosts connect locally, over SSH or through a reverse SSH tunnel.
3. Your armory is a Git repository of skills, rules and MCP server definitions. Enroll each tool target, preview its changes and deploy when you choose.

What you need.

• macOS or Linux, with Node.js 22 or newer.
• tmux on machines that run sessions.
• The command-line tools you want to use, installed and signed in with your own accounts. Antigravity sessions require the agy CLI; the desktop app alone is not enough.
• SSH connectivity between machines, or a reverse tunnel for a laptop behind NAT.

The hub and an agent can run on one machine. You do not need a fleet to start.

Your first steps.

1. Request early access and receive an invitation to the source repository.
2. Follow the repository README to build and install the agent, configure the hub and open the panel with a login link.
3. Launch a small managed session. Check its conversation and permissions from the panel.
4. Register an armory and enroll a tool. Preview before deploying, then add more tools or machines as needed.

An Android app for your own hub.

The early-access Android client (Android 11+) lets you read sessions and conversations, send messages and respond to supported questions or permission requests. Each response asks for confirmation. Pair it from the panel’s Phone section using a short-lived code or QR link; choose read-only or interactive access and revoke the device when needed.

Invited testers get the APK through their installation. There is also an installable web app. Your phone needs private connectivity to the hub and trusted HTTPS. This is not a public cloud relay or a Play Store release. The phone client does not administer machines, edit the armory or launch sessions. Optional Android background alerts are periodic, not real-time push.

A shared armory for your team.

Keep team skills, rules and roles in a versioned Git armory. Map it to the project directories where the team setup should apply, keeping personal work separate. Current team delivery uses a Claude Code project plugin; shared team sessions, team routines and team MCP sharing are not yet available.

The armory’s rule layers let you combine shared rules, per-node context and per-tool instructions. Common and node rules can include tool-specific blocks. Your personal armory distributes skills, rules and MCP definitions to enrolled Claude Code, Codex and Antigravity targets. Team repository access remains under your Git provider’s permissions; an invitation does not grant it automatically.

One panel. Honest boundaries.

The shared workspace does not make all adapters identical or move a conversation between providers.

Human control is part of the workflow.

A session can propose a change to armory files. A person reviews the reason and diff, then accepts or rejects it. Accepting updates the armory only. Previewing and deploying to enrolled machines is a separate step.

The dispatcher cannot answer permission requests. Tool execution also follows the permission mode and rules you choose; it does not mean every individual action always requires a new click. Write actions are audited. Armory deployments back up managed files and leave unmanaged configuration alone.

What stays yours.

Your tool accounts, machines, Git history and node-local secrets. MCP definitions reference secrets held on each machine instead of putting credentials into the armory. Longhall is detachable: unenrolling a target leaves its files in place.

A self-hosted panel is not automatically a public service. Keep the hub private or configure authenticated HTTPS access appropriate to your environment. The public project website is separate from your Longhall hub.