The open-source AI assistant that coordinates your coding agents—so you don't have to micromanage them.
Website · Why Pot? · Getting started · Agent Link · Documentation · Releases
Pot turns conversational goals into completed work. Instead of constantly micromanaging one-off prompts and fragmented contexts, Pot acts as a persistent assistant: delegating background tasks, coordinating external agents across machines, and only interrupting you when high-level decisions are needed.
Coding with agents has promised 10x productivity, but many developers find themselves exhausted—spending entire afternoons micromanaging AI, re-explaining repo habits across sessions, and inspecting code line by line.
Pot is designed around a simple belief: Human oversight should stay at the architecture level, while assistants handle the repetition.
- Assistants over one-off agents: Assistants run long-lived sessions, accumulating instructions, repo habits, and personal preferences without forgetting them across compactions.
- Goal delegation & background execution: Give your assistant a goal. It splits the work into background tasks, tracks progress, and brings finished results back to the conversation.
- Cross-machine hub: Run Pot headless on a Linux server, steer it through mobile Web UI, and dispatch coding jobs to Codex on your local Mac.
👉 Read the full design philosophy: Why Coding with Agents Is Exhausting
“Get this project ready to share: verify Linux installation, complete the getting-started docs, and prepare representative product screenshots.”
Pot can split that goal into background tasks for installation, documentation and screenshots. Results return to the same conversation: acceptance notes with remaining checks, a documentation draft, and images you can preview. Keep talking to refine the work: “Make the mobile screenshots larger; keep this docs version.”
Pot’s shared product UI with synthetic project work and background tasks. Click to enlarge.
Modern AI development doesn't happen in a single tool or on a single machine. Agent Link turns Pot into a universal mesh connecting your preferred coding agents, specialized bots, and remote instances—while preserving each agent's native models, credentials, and sandboxed workspaces.
- Cross-Computer Collaboration: Connect a headless Pot on your cloud server with your local developer workstation seamlessly.
- Independent Task Execution: Dispatched tasks run in isolated, persistent threads without jamming your active chat.
- Ecosystem Integration:
- Codex: Supported. Full bi-directional task delegation and review workflows via adapter.
- Claude: Coming soon.
- Grok: Coming soon.
- Antigravity: Coming soon.
Agent Link messages and returned review in the actual product UI. Click to enlarge.
Give this prompt to your agent to install and configure Pot on this computer:
Read https://github.com/jjyr/pot/blob/main/docs/install-with-agent.md and help me install and configure Pot on this computer.
The shared installation guide helps your agent check existing data, choose a channel and complete first setup. To install it yourself:
| Channel | Download / install | Platform |
|---|---|---|
| macOS App (Homebrew) | Use the two commands below; tap instructions | Apple Silicon, macOS 26+; first launch |
| macOS CLI (Homebrew) | brew install jjyr/pot/pot-cli after the tap below |
Apple Silicon, macOS 26+ for the current archive; CLI installation |
| Linux desktop · Experimental | Download .deb — select pot-desktop_VERSION_linux_amd64.deb |
Debian / Ubuntu amd64; requirements |
| Web UI (Docker) | View Docker image · ghcr.io/jjyr/pot |
Linux amd64 / arm64; installation and running |
| Web UI (Server) | Download Web UI / Server — select pot-VERSION-linux-ARCH.tar.gz |
glibc Linux amd64 / arm64; configuration and running |
brew tap jjyr/pot https://github.com/jjyr/pot.git
brew install --cask jjyr/pot/potInstall the independent headless CLI alongside the App with:
brew install jjyr/pot/pot-cli
pot-cli --version
# Upgrade the CLI through Homebrew:
brew upgrade jjyr/pot/pot-clipot-cli uses the existing CLI package, including Node and all runtime resources.
It has no GUI dependency. Use separate data roots when running it alongside the
App; see CLI installation.
During the unsigned release phase, macOS installation is offered through Homebrew only. Homebrew may still require an App-specific Gatekeeper allowance; follow the first-launch guide.
Linux download links open the official release selector; packages and the container
image await their first publication. The first brew tap
requires the explicit Git URL above. Once images are published,
choose an explicit version tag; no latest tag is published. Check release
notes and supplied checksums. If your package is unavailable, the
agent guide
covers the official source builds. GitHub-hosted files currently require
repository access.
Windows is currently unsupported.
Open Pot, choose Add assistant and connect an API model provider, another Pot, or Codex. Try: “Research this project and suggest three improvements.”
For Agent Link, copy connection information from one side into Add Agent on the other. See Agent Link or Codex setup.
With Git and mise installed:
git clone https://github.com/jjyr/pot.git
cd pot
mise install
mise run prepare
mise run build:go
.local/pot/bin/pot serve -root "$HOME/.pot-node" -ui 127.0.0.1:17703Leave it running. In another terminal in the checkout, get your login token:
.local/pot/bin/pot access -root "$HOME/.pot-node" tokenOpen http://127.0.0.1:17703, sign in with the token and add an assistant as above. The first run creates the private data root and token. For a remote server, forward the port from your computer first:
ssh -L 17703:127.0.0.1:17703 user@your-serverpot serve runs the Runtime; -ui adds its local browser interface.
pot web-ui-server is an independent browser service with a separate data root.
See deployment for that setup, TLS and services.
Agent Link supports Pot-to-Pot connections as well as Codex. To connect another Pot, follow the Agent Link guide. External assistant support is listed below.
Supported. Give this prompt to your agent on the computer running Codex:
Read https://github.com/jjyr/pot/blob/main/docs/connect-with-agent.md and help me connect Codex to Pot on this computer.
The assistant connection guide covers prerequisites, local plugin installation and pairing in Pot's Add Agent. For manual setup, see the complete Codex guide.
Coming soon.
Coming soon.
Coming soon.
Keep separate assistants for different goals, retain files and workspaces between tasks, and arrange scheduled work. Choose model providers and extend your assistants with plugins, MCP servers and Skills. Optional GitHub account setup and notification filters can bring project updates into the conversation. GitHub is not required to run Pot.
See installation and first configuration, Agent Link, Docker and the documentation index for operating instructions.
Licensed under the MIT License.