Question 1

What is StateSync?

Accepted Answer

StateSync is a desktop app that runs the coding agents you already pay for and gets the same work done for a lot less. Every agent sits in one place, there is nothing to set up, and the saving is measured rather than claimed: across 55 real tasks, the same work cost 46 percent less.

Question 2

Which coding agents does StateSync work with?

Accepted Answer

Claude Code, Codex, OpenCode, Cursor CLI, Copilot, Pi, Auggie, Factory Droid and Grok. You keep your own subscription or API key for each one. StateSync runs these agents rather than replacing them, and you can switch from one to another in the middle of a task without losing the conversation.

Question 3

How much does StateSync save?

Accepted Answer

In our TokenBench run on 55 real tasks across 8 repositories, StateSync did the same work for 46 percent less and 48 percent faster. That is 86 percent more work for the same money. Your own numbers will depend on your model and the work you give it.

Question 4

Are the savings the same with every coding agent?

Accepted Answer

Not yet, and we have not measured every agent. The savings on this site were measured mainly with Claude Code and Anthropic's models. Codex gets StateSync's tools too, but savings there may be slightly smaller depending on how you use it, because of how Codex handles tools from MCP servers rather than its own. The built-in tools in OpenCode, Factory Droid and GitHub Copilot are not as refined as Claude Code's, so StateSync's tools can save as much there or potentially more, though we have not published measurements for them yet.

Question 5

Does the quality of the work drop?

Accepted Answer

No, not on average. The easy way to spend less is to hide things from the agent, and then the work gets worse. Every task in the measured run was scored, and StateSync solved slightly more of them than the agent did on its own.

Question 6

I am on a flat-rate plan like Claude Max. What does StateSync do for me?

Accepted Answer

You get more work out of the same plan. Each task uses fewer tokens and fewer requests, so you go further before you hit a session or weekly limit.

Question 7

Why not just use /compact, or a bigger context window?

Accepted Answer

Different jobs. Compaction is for the end of a task: it summarises the chat so the next task starts clean, and mid-task it throws away detail the agent still needs. StateSync works inside the task, trimming each result as it arrives so every later request is smaller. A bigger context window raises the ceiling and the price per request, and sends the same material either way.

Question 8

Does StateSync change the model or the provider I use?

Accepted Answer

No. Same provider, same account, same model. There is no StateSync server between your machine and your provider.

Question 9

Do I need a password?

Accepted Answer

No. Signing in is a one-time code sent to your email (or Google or GitHub). There is no password to create, remember, leak or reuse. This is intentional, not a missing feature.

Question 10

Does my source code leave my machine?

Accepted Answer

No. StateSync never receives your code, your prompts, your chats, your commands or your voice. Your agent connects to its provider exactly as it did before, on your own account. StateSync does not change what that provider does with your data: the provider's own terms and privacy policy apply just as they do when you use it directly, including any use of your prompts and code to train its models, and StateSync has no visibility into that. What StateSync itself receives is counts: how much was used, which models ran, and a few facts about your installation. The privacy page lists every field.

Question 11

Does StateSync see my API keys?

Accepted Answer

No. Keys stay on your machine: they are kept in your operating system's secure store (or in your agent's own config file) and passed to your agent when it runs. StateSync has no key proxy: there is no StateSync server in the path between your machine and your provider's API.

Question 12

What does it cost, and how does the trial work?

Accepted Answer

Pick the plan that matches what you already spend on coding agents. Plans run from $8 to $100 a month. The trial is 14 days free for the first 50 places, 7 days after that, on whichever plan you pick, and a card is needed to start. Cancel before the trial ends and you are not billed. Otherwise the plan you picked starts at the price shown.

Question 13

What do I have to configure?

Accepted Answer

Nothing. Install StateSync and open a folder. The agents already on your machine are found for you. No config files, no plugins, no per-project settings. There are advanced settings if you want them, for things like which voice model to download.

Question 14

Can StateSync break my agent or my work?

Accepted Answer

StateSync is built not to. When StateSync is not sure what a result needs, the agent gets the whole result. If something does go wrong, please tell us at support@statesync.net, or use Support in the app's settings.

Question 15

What is StateVoice?

Accepted Answer

Voice dictation built into StateSync. Press a key and talk, or hold it if you prefer, and clean text lands in the prompt. StateVoice runs entirely on your machine, so the recording never leaves your computer.

Question 16

Which operating systems does StateSync run on?

Accepted Answer

Windows, macOS and Linux. StateSync is a native desktop app, and the quickstart page shows which builds are out right now.

Question 17

Who runs the benchmark, and can I check it?

Accepted Answer

TokenBench 55-task set. StateSync was run on 11 September 2026 against the plain agent's runs of the same tasks from 22 to 24 August 2026. 55 tasks across 8 repositories and 6 categories, Claude Sonnet 4.6, one StateSync run per task against the plain agent's 4 to 14 runs, averaged. We ran TokenBench ourselves and no independent run has been published. Every task and the harness are public on the TokenBench GitHub, and you can run the same tasks against any tool yourself.

StateVoice dictation

Starting and stopping

Transcribed on your computer

Choosing a speech model

Microphone

Cleaning up the text

What leaves your computer