Syntic Desktop gives you two ways to work with the platform: Chat and Code.
Chat is the same Syntic you know from syntic.ai, plus quick entry, screenshots, dictation, and connectors that come from running natively on your computer. Code is for building software, from writing and testing through deploy.
Code runs on Syntic CLI underneath — local to your machine, capable of independent work, able to spin up sub-agents and sustain long jobs. That's how a single dispatch can build software end to end.
Each mode is designed around the work it serves, showing you what matters and giving you control where you need it.
Chat
Chat is where you think out loud: ask a question, draft an email, sum up a long document or talk through a decision. Your conversations are the same ones you see on the web, so you can start on one device and pick up on another.
Because the app runs on your computer, Chat adds a few things the browser can't:
- Quick entry. Open a small prompt from anywhere with a keyboard shortcut, ask, and get back to what you were doing.
- Screenshots. Capture part of your screen and drop it straight into the conversation — an error message, a chart, a design you want feedback on.
- Dictation. Speak your request instead of typing it, which helps when the thought is long or your hands are busy.
- Connectors. Link the apps and files you already use so answers can draw on your own documents, calendar and email instead of starting from nothing.
Code
Code is for building software. Open a project folder, describe what you want, and Amara works through it the way a developer would: reading the code, making the change, running the tests and checking the result.
You stay in control
Every edit shows up as a change you can read before you accept it, and Amara asks before running anything that could affect your machine. You can stop a task, redirect it or take over at any point.
Built for longer work
Because Code runs on Syntic CLI, it can keep going on bigger jobs — a feature across several files, a refactor, a round of failing tests — and split the work between sub-agents when that's faster. Leave it running and come back to a finished change that's ready for review.
Which one to use
Use Chat when the answer is the goal: an explanation, a draft, a summary. Use Code when the goal is working software in your project. You can switch between them at any time from the same window.