Blog
The big updates, the stories behind them and what is planned next.
-
Shuriken speaks nine languages
The Shuriken app runs in English, Arabic, Spanish, French, Japanese, Korean, Brazilian Portuguese, Russian and Simplified Chinese, set in Settings. -
Why our phone apps are native, not a web view
Our phone apps go native in November 2026, because a web view is weak at the keyboard, gestures, sheets, haptics and push. The web app stays. -
How we test switching for days at a time
We test switching on a fake clock. One run gives twenty sources four days, with a 30-minute outage every night and a refused sign-in every hour. -
Pinned chats, queue and alerts on every device
In Shuriken 5.1, pinned chats, the queue and notifications stay in step on every device. How the sync works, and where we're still improving it. -
Point at the page and say the change
In Shuriken's browser, turn on Design, click an element and say what should change. Your agent gets the element, a cropped screenshot and your words. -
Sleeping chats: less memory, same history
Idle Shuriken chats sleep after 20 minutes: the agent process closes to free memory, and your next message wakes it. What 5.1 adds to sleep. -
Heroin mode comes to Windows and Linux
Shuriken 5.1 keeps Windows and Linux computers awake for your coding agents, lid closed included where the machine allows it. Same name, same warnings. -
Claude Code pull requests that merge themselves
Land a coding agent's branch as a GitHub pull request with auto-merge on, so it merges once your checks pass. When to use that and when Finish is enough. -
Gemini CLI, set up as easily as Claude
Shuriken 5.1 sets up Gemini CLI like Claude Code: install it in setup, add Code Assist sign-ins and paid API keys as sources, see allowances, switch. -
Codex as a subagent of Claude Code, and the other way round
In Shuriken 5.3 the agent in any chat can start background agents and chats on Codex, Gemini CLI and your other providers, each with hot swapping. -
Many dev servers, many worktrees, no port fights
Parallel Claude Code worktrees all want port 3000. How Shuriken finds dev servers, hands each worktree its own port, and tips that work without it. -
Claude Code denyInsteadOfPrompting: runs that don't stall
Claude Code 2.1.319 adds permissions.denyInsteadOfPrompting: a tool call that would wait on a permission prompt is denied and the turn carries on. -
Ollama and LM Studio as sources
Use LM Studio or Ollama with Claude Code or Codex: add a local model as a source in Shuriken in three steps and test it. It runs on your own computer. -
Claude break reminders: take the break, keep the agents
Claude's break reminders sit in Settings › Wellbeing and nudge you after a daily amount of time. Take the break; your coding agents can keep working. -
Will Claude plans get cheaper? What the record shows
Will Claude plans get cheaper? Not in price so far: Pro has been $20 a month since 2023, the $100 and $200 tiers unchanged since 2025, as API prices fell. -
Your voice stays on your computer by default
By default Shuriken turns speech into text on your own computer with NVIDIA Parakeet, offline and private. Or use your own key for a live speech provider. -
Why we call Shuriken a harness
Since 21 October 2026 we call Shuriken a harness: it runs Claude Code, Codex and 65 more agents with your own accounts, tools and devices. -
MCP servers, set up once for chosen projects
Turn an MCP server on for every project or only the ones you pick. Your agents' chats there get it, and one sign-in covers them all. -
How MCP sign-ins travel between your devices
Sign in to an MCP server once and every device of yours has it, servers included. Our cloud stores it sealed, and keeps a key that can open it. -
How our encryption works, with the code
Every key Shuriken makes, the relay handshake, what is sealed to whom and the known limits, on one page with the encryption code read at each build. -
Max 20x is now Ultra: no 5-hour limit once verified
Anthropic renamed Max 20x to Ultra and drops its 5-hour limit for verified accounts. What changed, what stays, and what Shuriken does about it. -
Shuriken's new design, and how we keep it
On 21 October we rebuilt Shuriken's design system: tokens, one toast, one icon set, calmer screens and a test that refuses one-off UI. Before and now. -
Shuriken on Linux: AppImage, .deb, x64 and Arm
A desktop app for Claude Code, Codex and 65 more agents on Linux: AppImage or .deb, x64 or Arm, ChromeOS too, plus a headless server mode. -
How we keep your data safe
A security engineer told us he wouldn't use a closed-source app he couldn't check. What we changed, what our cloud can't read, and what it still can. -
Shuriken is officially launched, in beta
The harness for Claude Code, Codex and other coding agents is open to everyone. It began as our internal tool; here is what it does and what beta means. -
What's new in Shuriken 5.1
Shuriken 5.1 adds sign-in with Google, Apple or an email code, Allow and Always allow at a MacBook's notch, and billing and fuel in Sources. -
How Shuriken started: a tool we built for ourselves
We build software for clients and ourselves. No harness fit how heavily we use AI, so we built our own. Then a programmer asked: why don't we sell this? -
Shared projects beta: share a project with a friend
Shared projects (beta) let a friend work in one of your projects on your computer, with your files and your Claude. Both sides opt in; sharing needs Pro. -
We were tired of logging in and out of Claude
Limit reached, /logout, /login, paste the context back. We did it so often we built Shuriken: chats move to an account with room by themselves. -
The 5-hour clock starts when you do. So we start it.
Claude's 5-hour window only starts when you use an account, so an idle one wastes time. Shuriken starts its clock with one tiny background request. -
Hot swapping: chats that move when an account runs out
Hot swapping AI accounts, the way Shuriken does it: your running chats move to another of your accounts when one nears its limit. What happens at 99%. -
API keys as a last resort, with a spend cap
Let Claude Code fall back to an API key only when every subscription is out, with a spend cap on each fallback run. How it works in Shuriken. -
How Shuriken picks the next account
At your switch point (99% by default) or a limit, Shuriken moves your chats to the source with the most room. Expiring capacity goes first, API keys last. -
Codex with more than one ChatGPT account
Add each ChatGPT sign-in you own as a source. When one reaches its Codex limit, Shuriken moves your Codex chats to the next and they carry on. -
Best MCP servers for Claude Code (2026)
Our MCP picks for Claude Code, by job: GitHub and Sentry, Linear and Notion, Context7 and DeepWiki, Playwright, Supabase, Neon, PostHog and Stripe. -
Your agents on your phone, from the browser
Open app.shuriken.sh in any phone browser and add it to your home screen: every chat, the queue, Changes and voice. Browsers never count as devices. -
We're building native iOS and Android apps
Two native phone apps for Shuriken, iPhone and Android, are planned for November 2026. Until then, phones use the web app at app.shuriken.sh. -
Claude Code and Codex in one project
How to use Claude Code and Codex together on one project: a chat per agent, one set of MCP servers for both, and each agent on its own sources. -
A git workflow for Claude Code that keeps main clean
The Claude Code git workflow we'd give anyone running several agents: a branch per task, small commits, read the diff, checks before merge, then squash. -
How to review AI-generated code without reading every line
We review agent diffs tests first: would each test fail without the change? Then deletions, the diff's edges, secrets, and a run. Our real misses. -
Test-driven development with Claude Code
Claude stops when work looks done, so give it a failing test to run. Our TDD prompt in three steps, and a Stop hook that runs tests when Claude finishes. -
Keep awake only while agents work
Keep your computer awake while an agent, the queue or a workflow runs, then let it sleep. Shuriken's two settings: While working and Always. -
Yes, it's called Heroin mode
Heroin mode keeps your Mac awake with the lid closed, so your coding agents keep working. Why it has that name, how it works, and the honest warnings. -
A notification when a chat needs you
Get a desktop notification when Claude Code or Codex finishes, asks a question or wants approval. The DIY hooks route, and what Shuriken does for you. -
Shuriken on Windows 10 and 11
Run Claude Code, Codex and 65 more coding agents in parallel on Windows 10 and 11. Installer or .zip, x64, with signed updates. -
Every plan and key you own, working as one
Add your Claude, ChatGPT, Gemini and other plans and API keys to Shuriken as sources. When one runs out, your chats move to the next. -
Fork a chat from any reply, then merge it back
Try another approach without losing the first: fork a Shuriken chat from any reply, keep the fork under its parent, then merge its work back in. -
Two Notion workspaces, one MCP list
Add Notion twice, once for work and once for personal, each with its own sign-in, and pick which projects get which. Switching accounts never asks again. -
Your agents run on your machines, not ours
Shuriken runs coding agents on your own computers and servers. Our cloud links devices and relays sealed messages. Why we chose local, and the trade-off. -
Bring your own plans: we never bill model usage
Shuriken runs Claude Code, Codex and other agents with your own subscriptions and keys. We never resell tokens or add a margin. -
Point at the page: Design mode for coding agents
Click an element in your running app, write the change, and your coding agent gets its details and a cropped screenshot. No more describing buttons. -
Distribute: spread work across accounts on a clock
Two modes: Rotation moves your chats only when an account runs out; Distribute moves them every 15 to 60 minutes to the one with the most left. -
Finish: checks, rebase and merge in one click
A Shuriken chat can work on its own branch. Finish commits what's left, rebases, runs your checks and squash-merges it, then cleans up. -
Shared projects: who gets what access
Shared projects are an opt-in beta in Shuriken 5.1. The trust model: what a member can reach, the controls you keep, and who to invite. -
Why chats said "Connection lost", and the fix
On 5.0.0, one very long chat could freeze Shuriken's background service: "not reached" blinking, window reloads, stopped agents. The cause and the fix. -
No more waitlist: you're a Founding member
On 21 October 2026 the waitlist ended: everyone who signed up before launch, by account or email, gets Pro at no charge for as long as Shuriken runs. -
Shuriken 1.0: why we called it 1.0 after five days
Shuriken 1.0 shipped on 4 October 2026, five days after the first prerelease. Why we called it 1.0, what changed, and the 1.1 that followed that evening.
The first posts go up on launch day.
Try Shuriken on your own computerYou're signed in
Add your Claude, Codex and Gemini accounts once. Shuriken switches between them so your agents keep working.Your accounts, projects and chats are in the app.
