One conversation. Work you can follow.

From conversation to delivery checkpoints

Ask a question, explore an approach, or propose a deliverable in the same conversation. Simple questions need not start a project workflow. Work that needs execution can be planned with scope and required checks; completing a deliverable does not close the chat.

Automatic where permitted. Explicit where it matters.

Your selected governance mode and effective policy determine which actions may run automatically, need a proposal and approval, or are prohibited. Review approvals and actionable blockers in the conversation. You can decline, cancel, or give a new direction; redirection takes effect at a safe boundary rather than silently rewriting work already running.

Execution budgets can limit model calls, logical tokens, and provider-active time. A capacity increase follows the existing policy: automatic within allowed limits, proposed for approval, or denied. More budget does not grant more permissions or remove repair and retry safeguards. These resource limits are distinct from a provider's subscription allowance or an exact currency cap.

If work cannot safely continue, Syncore preserves evidence and explains what needs attention. Repair is bounded, not guaranteed. Interrupted work with uncertain effects may require inspecting the files and resolving recovery before a fresh attempt; the old operation is not blindly replayed.

Retained history. Bounded model context.

Search conversations and recorded sources, load older turns, and inspect project associations. Raw conversation history remains retained until deleted; provider prompts stay bounded. Older turns may be summarized and selected for relevance. This is not an unlimited model context window or a promise of perfect recall.

The Context panel distinguishes Sent to model, Prepared, not sent, Available by reference, not sent, and Not sent to a model. Merely appearing in Context does not mean an item was transmitted. Historical or runtime-internal activity may not have complete source records.

Selecting a project is an association, not blanket permission to read, change, or transmit all its files. Authorized retrieval and execution remain subject to their own boundaries.

Providers and requirements

Windows 10/11, x64; an approved Syncore account; and a separately configured model connection. The desktop uses local SQLite and does not require Docker or PostgreSQL. Internet access is required for account sign-in/admission, remote providers, and any missing installer or runtime components. macOS and Linux consumer downloads are not available.

Provider accounts, API billing, model availability, and vendor terms remain separate from Syncore. Supported connections and qualification notes below were reviewed September 26, 2026; live checks cover specific models and runtime versions, not every model a vendor offers.

Use Models & Providers in Syncore to configure connections and inspect available models. No connection grants unrestricted project access. Not all language SDKs, architectures or installation mechanisms are qualified.

Install the app. Connect your tools.

1. Sign in and apply

   Use a supported identity provider and complete your private-beta application. Sign-in alone does not grant access.

2. Download after approval

   Open the download center for the latest available beta, release notes and checksum. The current direct installer is unsigned and is not a Microsoft Store release. Follow the installation guidance and start with a disposable project.

3. Connect a model provider

   Authenticate the selected connection and review provider consent. Provider runtimes are installed separately when needed; account sign-in to Syncore is not sign-in to a model provider.

Local-first, not entirely offline

Review provider consent and managed local-data controls in Syncore, and read the Privacy Policy for the published policy. Local storage does not mean a remote provider never receives context.

How to read the historical benchmarks

The homepage reports internal Codex subscription-backed runs recorded July 10, 2026. The seven-scenario suite recorded 144,941 tokens, 51 provider calls, 610.567 seconds and 7/7 accepted scenarios, with zero recorded lifecycle anomalies. These are historical observations, not current-release, independent external, or Microsoft certification.

The three showcase records are separate recorded benchmark examples, not customer deployments. Their instructions are representative and shortened. The site does not expose raw repositories, code diffs or provider transcripts. Do not combine showcase timings with the suite into a new aggregate.

The internal artifact-check score starts at 100, subtracts 25 for each error and 5 for each warning, and is floored at zero. The checks examine issues such as syntax, API changes, test strength and scope. A 97.86/100 average is not a correctness percentage or security guarantee.

Tokens were available for these recorded runs. Subscription-backed usage did not produce a defensible per-run dollar invoice; model billing is separate from Syncore. Other providers may omit telemetry. Total usage alone does not prove context savings or superiority over direct model use.

Direct comparison recertification remains pending. These records do not supply a current build/model manifest, repeated-run distribution or public reproduction bundle; they are historical examples, not a reproducible current-release comparison. Any future performance comparison needs matched tasks and models, repeated trials, and outcome-quality gates.