Overview
Connect your models. Do the work. Keep the context.
This guide covers the Electron desktop app and the synoec CLI.
Both run on the same engine and share configuration, history and permissions,
so most pages apply to both. Each page is a short summary, how to use it, an
example and its honest limits.
Start here
Section titled “Start here”- Getting started: install, connect a provider and send a first message.
- Desktop tour or CLI: learn your client.
- Providers and models: connect providers and choose a Profile’s models.
Use Synoec
Section titled “Use Synoec”| Page | What’s in it |
|---|---|
| Desktop tour | The three areas, composer, Thread rail, subthreads, Workbench, Settings, appearance and shortcuts |
| CLI | The interactive terminal, slash commands, headless runs, recipes, schedules and subcommands |
| Ergon | Agent companies: seats, Specialists, models and the org chart |
| Agora | The built-in browser, Browser chat and tab grants |
| Lysis | Reverse-engineering investigations and analysis engines |
| Tasks and subthreads | Modes, Focus, Specialists, Tasks, subthreads, recipes and schedules |
| Tools and integrations | Built-in tools, sandbox levels, web search and scraping, MCP, plugins, Skills and Computer Use |
Configure
Section titled “Configure”| Page | What’s in it |
|---|---|
| Providers and models | Connections, Profiles, the default chat model and the model choice for Tasks and subthreads |
| Usage and pricing | Composer usage rings, Spend, provider and model overviews, estimates and budgets |
| Local AI | Running models on this computer: runtimes, GPU sizing and the automatic Connection |
| Decision models | System One decision models and decision-based discovery |
Context and memory
Section titled “Context and memory”| Page | What’s in it |
|---|---|
| Workspaces and memory | Workspaces, projects and scoped memory |
| Context and learning | The Context surface, imports, the context index, recall and reviewed lessons |
| Repository | The code index, codebase map and project instructions |
When something goes wrong
Section titled “When something goes wrong”Troubleshooting maps symptoms to a first check: recovery after a restart, provider sign-in, diagnostics and where your data lives.
For maintainers
Section titled “For maintainers”| Page | What’s in it |
|---|---|
| Architecture | Runtime ownership, storage and recovery |
| Releases | Versioning, packaging and publication |
| Licensing | Dependencies, bundled runtimes and notices |
Contributors should also read definitions for product terms, specifications for requirements, repository layout for package boundaries, and TESTING.md for test tiers and rules.