The IDE workspace where agents ship alongside your team: live multiplayer coding, merge conflicts that resolve themselves, and team chat where the work happens.
Secure your spot and be among the first to try Smirky. Invites roll out in order.
Live multiplayer coding Teammates and agents share cursors, selections, and live buffers in the same workspace, so work stays visible as it happens.
Agent-resolved merge conflicts When branches diverge, the agent explains both sides and proposes a diff you approve.
Team chat & presence Built-in team chat with presence and @mentions. No context-switch to a second app to say “look at line 42.”
Software work is becoming orchestration. Teams still ship together, but more of the work now happens through agents: asking, reviewing, testing, merging, and approving. Most IDEs still assume one person typing alone.
Smirky is the workspace for that new loop. Humans and agents share one project context: files, git, terminal, chat, diffs, and approvals. When you step away, Smirky keeps a record of what changed and what needs your attention.
When your branches disagree, the agent reads both sides and hands you a clean diff to approve.
Mark renamed count to clicks while you added a reset button that still references count. I can keep both changes: adopt the rename and point your handler at clicks.
Step out for lunch, come back to a digest, not archaeology. Smirky summarizes what your teammates and agents changed, whether it touches your work, and what needs your attention.
The headline: Mark merged the header refactor into main, so your branch is now behind. Joyle reworked the button and the agent quietly fixed a lint error. Nothing touches what you're editing.
Mark merged the header refactor into main
1hJoyle pushed 3 commits to Button.tsx
48mAgent auto-fixed a lint error in format.ts
30mPeter opened a PR for index.css
12mSmirky turns agent work into visible steps: reading files, searching the repo, proposing diffs, and running checks. Pick the model, speed, project context, branch, and permission level before the run starts. Changes land as reviewable diffs, not mystery edits. Prefer your own harness? Bring it along.
Tool calls in the open Reads, searches, edits, and terminal commands appear as visible steps, so you know what happened before you approve the result.
Diffs before changes Agent edits arrive as file diffs with apply and reject controls, keeping humans in the loop where it matters.
Project context included The agent works against the open folder, current branch, selected files, local tools, and the permissions you choose.
Smirky is built for the agents developers already use. Connect Claude Code, Codex, or opencode, and bring their work into the same shared workspace as your files, git, terminal, chat, and approvals.
Your tools, your account. Smirky connects to CLIs you already have installed and signed in. No second subscription, no key juggling.
Full workspace context. Connected agents work inside the same project context as your team: files, branch, diffs, terminal, and approvals.
Mix and match. Send the refactor to Claude Code and the test cleanup to Codex. The work still lands in one shared flow.
Picked up the refactor. Working in Header.tsx
Agents can work with the same project surfaces you do: terminal, branches, diffs, commits, and local files, with sensitive actions gated by permission.
A real terminal A true shell with a persistent working directory, live output, and signals, not an emulation of one.
Native git Status, staged diffs, commits, and pushes run against your actual repository, the same git you'd use in a terminal.
Real-time everything Presence, chat, and shared state stream over live channels. You see teammates the moment they show up.
Local-first Your code stays on your machine, and sensitive agent actions are gated behind your explicit approval.
We build Smirky in the open, alongside the developers who use it. Every message is read, and your feedback moves the roadmap.
“Let me watch two agents work side by side, one terminal each.”
Maya · 128 backing
In the next build. Thank you, Maya.
Feedback reaches the people building Smirky, and we answer.
What ships next is decided with the community, not for it.
Progress ships early and often, so you always see what's next.