ARCHITECTURE

Every surface an actor.

A human and an agent reach the same surface through one bridge, with the same methods and the same permissions. The rest of this page is what those surfaces are, how they are named, and how they move between machines.

The AI has no surface of its own.

So today it reaches your work three ways, and none is clean. It fakes the interface, computer use driving your mouse, screen recording watching your display, pixels streamed to a model somewhere else, brittle and blind to the state underneath. It goes headless through APIs that never touch the interface you actually work in. Or it is bolted inside an existing app, a browser, a doc, a chat, so your work and your agents scatter across a dozen of them.

THE AI Computer use Headless APIs Copilots in apps fakes the interface never touches your UI scattered across apps
Three ways in, not one a clean path to the surface you work on.

Every one of these fragments the experience, because there is no clean way for an agent to reach the surface a human actually works on. Port42 is that surface. A port is a live, addressable actor that a human and an agent drive through the same bridge, with the same permissions. One place, not a dozen. No pixels, no puppeteering. The rest of this page is how that works.

A port is a live, addressable actor.

You send it queries, it emits updates. The same contract whether it is a terminal, a chat, a web surface, or an agent. Local, on another machine, or a peer.

query → A PORT terminal · chart · doc · agent → updates

One bridge, every caller.

Every way into a port goes through the same bridge. You through the UI. An agent as tools. The CLI, the REST API, another Port42 gateway over the wire. One implementation, one permission model, no adapter, and no separate "AI mode." When two callers hold the same port at once, right-of-way decides who acts, so you can take the pen from an agent mid-task and hand it back.

You · the UI An agent · as tools The CLI The REST API Another gateway ONE BRIDGE same methods · same perms A PORT live surface

Your space stays. Everything else swaps.

Port42 is your space, the one invariant layer, where every port lives and one bridge drives them. Your agents, memory, and knowledge plug in from below. Your domain tunes it from above, as packs. Port42 itself never learns a domain, an agent, or a body of knowledge.

THE PERSON PACKS your domain, plugged into Port42 as config · dev · research · ops · never in the core SWAPPABLE tune the space YOUR SPACE INVARIANT holds your ports, driven by one bridge presence · permissions · right-of-way · undo · addressing (port42://) consumes PLUGS external systems you bring, kept on your machine SWAPPABLE AGENTS Claude · Codex · any MEMORY your own, on your disk KNOWLEDGE vaults · docs · RAG

Two swappable ends, one invariant middle. Change your agents, change your memory, change your domain. The space stays. That is the part that is yours.

Many agents, one surface, no trampling.

These come built into Port42, capabilities it provides, one job each. Together they are why a whole team of agents can share one surface without trampling each other, or you. You bring the agents; this is what keeps them in line.

Watcherwatches every agent
Gatekeeperdecides what reaches you
Controllergrants and limits access
Coordinatorhands off, no clash
Guardundo and guardrails

Reach any port, anywhere.

Every surface gets a stable address, so where it runs stops mattering. You reach a port on another machine exactly as you reach one on your own, and others reach yours. Gateway to gateway, spaces link into a network, all of it on your own machines, peer to peer.

The addressport42://[type]/[id]/[path] · a stable name you can point anything at, not just files but agents, spaces, and relations too.
Same call, any distanceA port on another machine answers the same request as a local one. Remote is never a special case.
TemporalA port "as of T" is a first-class address. History and undo fall out of it.
On your machineLocal-first and end-to-end encrypted. Your data stays with you, nothing to export.
Ports moveA port serializes completely, so you can hand it to another space and it arrives running.
Peer to peerAcross machines it runs over libp2p (Circuit-Relay, DCUtR), no server in the middle.

Tailor the whole experience to you.

Port42 wraps the layers that change, the AI that executes, the memory it keeps, the knowledge it draws on, behind stable, versioned interfaces. Swap any one, or all of them, and nothing above breaks. The interface is yours too, build the ports you need, tune it with packs, arrange the space your way. Bring your own AI, memory, and knowledge, and shape the whole experience around how you actually work.