polycode
An agentic coding CLI. Runs on your machine with a free hosted tier. One command, no setup. macOS, Linux, and Windows.
A coding agent you can install in one command.
polycode is the runnable output of the compile primitive from the Polylogic research program. It runs a standard agentic loop — you ask, it thinks, it uses tools, it returns a result — but every turn lands as a SHA-256 chained row in a session log you own.
It ships with a free hosted tier so the install is one command with zero environment variables. Users who want unlimited throughput can paste a free Groq, Anthropic, or OpenAI key into the masked /key prompt and polycode hot-swaps the session to talk directly to their provider.
Our coding agent. It happens to do more.
polycode ships with a small, honest tool surface. It writes code, builds websites, makes images, reads images, searches the web, and remembers what it learned with you. Routing happens invisibly. You type, polycode picks the right provider.
No install. Open the playground, ask polycode to build something, watch it appear in the Canvas. Sign in with email to save your workspace across sessions.
Open the playground →polycode can generate images from a prompt, read images you give it, and search the web for current information. All behind one interface. polycode picks the model. No keys needed.
Try a prompt →Sign in once and polycode's canon (the SHA-256 chained session log) persists across reloads and days. Your prior turns come back. You can download the whole log at any time.
Sign in to save →Nine tools. Zero configuration.
Run a shell command in the working directory. 30-second timeout, sandboxed.
Read, write, and surgical-replace files relative to the working directory.
List files matching a pattern. Pure-Node, works identically on macOS, Linux, and Windows.
Regex search across files. Pure-Node, no shell-out.
Analyze a local image file via a vision model. PNG, JPEG, WebP, GIF up to 4 MB.
Generate an image from a text prompt. No key required on the hosted tier.
Fetch a web page, API, or GitHub file. HTML is converted to readable text. Refuses private networks.
Search the web for current information. Routed through the Polylogic hosted proxy with a free fallback.
Write an HTML file and open it in the browser. Useful for charts, sites, and anything visual.
How polycode stays safe.
polycode runs inside the directory you open it in. Every tool call is sandboxed to that directory. No uploads to any server except the inference proxy, and that endpoint receives prompts only, never file contents.
Every turn, every tool call, and every model response is appended to a SHA-256 chained JSONL file at ~/.polycode/canon. Run `polycode --verify` to confirm the chain. Replay your own history, hand it to a teammate, or back it up.
A local secret scrubber blocks any chat message that contains a recognized API-key pattern before it reaches the model. To save a key, type /key in the REPL (or run `polycode login` from your shell) and paste into a masked prompt. The key lands in ~/.polycode/secrets.env with chmod 600. The model never sees it.
Paste 500 lines of logs, a stack trace, or an error message and polycode collapses the display to [Pasted #1 (20 lines)]. The full content still goes to the agent — only the display is compressed. No terminal flood.
Node.js 20 or newer. macOS, Linux, or Windows.
No API key required. The free hosted tier routes through the Polylogic inference proxy at 60 turns per hour per install.
- Attach anything.
- Text, data, code, PDFs, or photos. Drop them in or snap one from your phone. Publish any site in one click to polylogicai.com/p/yourname. Generated images now show up on both the preview and the published page. Clearer errors, friendlier prompts, undo on anything destructive.
- The web playground now runs a multi-modal router behind one interface.
- Ask polycode to generate an image, analyze one, search the web, or fetch a URL.
- It picks the right free-tier provider for you.
- Sign in to save your workspace across sessions via the SHA-256 chained canon.
- CLI and web now share the same file organization rule.
- Folders named after what you are building (bakery/, calculator/, chart/), never generic /project/.