Parallel agent cockpit
See every tmux workstream as a card with provider, model and working/waiting state, then focus the live terminal without hunting through shells.
04
04 / Local AI-agent operations console
Server Harbor
Server Harbor is a security-first local command centre for teams operating servers and many AI coding agents at once. It joins a live tmux session cockpit with host health, Kubernetes, traffic, governed logs, transfers, documents and audited agent interaction.
Not a concept render
This is the product.
Live product evidence: 13 simultaneous sessions in the captured operating view; Codex/Claude detection and six adapter families; readiness-aware queues; host/Kubernetes/traffic/log views; controlled attachments; localhost-only access; and content-minimising audit.
Server Harbor capabilities
More than the headline feature.
Server Harbor is a connected product system. These capabilities are implemented in its current architecture, interfaces and operating workflows.
Six semantic CLI adapters
Understands Codex, Claude, Gemini, Aider, Kilo and OpenCode commands and controlled menu interactions instead of treating every terminal as raw text.
Review-first follow-ups
Queue the next instruction, review it, and optionally send only when the selected agent is actually ready.
Host and Kubernetes health
CPU, memory, RAID, disk, processes, failed services and workload health sit beside the agent sessions acting on them.
Traffic and governed logs
Inspect per-application ingress activity, masked addresses and allowlisted journal/file logs through a no-shell privileged broker.
Safe message and file delivery
Deliberately unlock input, preserve bracketed-paste semantics, attach files with 0600 permissions and divert oversized prompts to reviewed attachments.
Localhost security model
The current console is loopback-only, reached by SSH tunnel, authenticated by an HTTP-only session and never exposed as public server administration.
Useful audit without prompt capture
Record login, safe action and terminal-send events while deliberately excluding the sensitive message contents from the audit log.
Used by Infinovation
This site was rebuilt while Harbor coordinated the agents
Server Harbor is not an imagined future dashboard. During this work it was actively coordinating this Codex session and multiple other agents. The captured interface contains 13 real concurrent workstream cards with project names and paths replaced before the image was written.
Real-world comparison / Portainer, Rancher, Lens, tmux and agent dashboards
Server Harbor belongs in the actual market conversation.
Compared with Portainer, Rancher, Lens, tmux and agent dashboards on the work each product is designed to do. This is positioning by architecture and workflow—not a claim that every product serves the same user.
Market axisNamed alternativesServer Harbor
Container operationsPortainer provides a visual management layer for Docker, Kubernetes and edge environments.Server Harbor adds the human/agent work layer: live coding-agent sessions, reviewed input, queues and their immediate server context.
Kubernetes managementRancher manages clusters at enterprise scale; Lens provides a rich Kubernetes desktop view.Harbor is the local operations room where host, K8s, traffic and the terminal agents changing those systems meet.
Terminal multiplexingtmux is the proven session engine for persistent terminal work.Harbor keeps tmux underneath and adds discovery, provider-aware state, a visual grid, safe composer, attachments, queues and audit.
Agent control centresModel-specific dashboards coordinate tasks inside their own agent environment.Harbor coordinates heterogeneous CLI agents already running on your server and connects them to actual infrastructure operations.
Common questions
About Server Harbor
Is Server Harbor available?
It is used internally and in a private enterprise beta. Public release plans are still being shaped around security and operational feedback.
Does it work with Claude Code and Codex?
Yes. The current console detects and manages Claude Code and Codex terminal sessions, with an adapter model for other terminal agents.
Is it exposed to the internet?
No. The current design binds to loopback and is accessed through an SSH tunnel. Avoiding a public control plane is a central product decision.
Start a conversation
Interested in Server Harbor?
Use it now, or talk to us about how it fits your software and infrastructure.