Loading…
Poly is an AI workspace with chat, research, documents, images, self-reflection and trading agents. Enter the workspace ·
Everything we've shipped, everything we're building, and the order we're building it in.
3 in progress · 3 planned
Up next
Poly CLI
Shipped
The first closed build, put in front of a handful of people to find out what was actually usable.
The first three surfaces opened to everyone: generation, documents and one conversation across several models.
A terminal client for the platform, and direct model selection with routing between the models we offer.
Self-report questionnaires based on published instruments, scored locally, and an IDE that runs the code it generates instead of taking it on trust.
Plans, sources and synthesis on a real flow engine, so a question becomes a reproducible pipeline rather than a chat log.
Mail with real send and receive, workflow automation, and shared workspaces holding every artifact the platform makes.
Trading from wallets you connect, with strategy agents that run on measured rules — and refuse to act on anything unmeasured.
Poly alongside whatever you are already reading, sharing the same account, history and capabilities as the workspace.
In progress
The whole platform from a terminal — capabilities, agents and workspaces addressable as commands.
An evaluation pipeline for the models the platform runs on, scored on absolute metrics rather than a leaderboard.
The next platform release, consolidating every section onto one capability layer.
Planned
Native clients for the surfaces that belong in a pocket: chat, capture, review and approvals.
A first-class desktop client with local model support and the filesystem access a browser cannot give.
Every surface, client and capability addressable from any of the others — one system rather than a suite that shares a login.
Considered and dropped
Tilt / pointer-tracked card effects
Cut in favor of the connectome as the landing's interactive signature — one strong interactive surface beats several decorative ones.
Documentation hub
Volume-gated: ships when there is enough platform documentation to fill it (Circuit D).
Per-kind article permalinks
Rejected: the RSS guid base /news/{slug} is frozen forever, so permalinks stay kind-agnostic. Kinds arrive as feeds/tabs, not URL changes.
No roadmap announcements yet.