Alpha + source preview

Install the app, or run the newest source.

The desktop alpha is a real packaged SkyTwin app built from the current source. It supports first-account setup with a Google OAuth client you create and control; current source also includes a guarded fictional sample when you prefer not to connect an inbox.

Choose the right path

Fastest hands-on path

Download the desktop alpha

Open a packaged app on Apple Silicon macOS, x64 Windows, or x86-64 Linux. No repository checkout is required. The build is unsigned and can connect your real Gmail inbox through the desktop-local dashboard and your own Google OAuth app.

Newest capabilities

Run the source tree

Use the repository to inspect the latest decision/policy boundary, run the newest sample, or operate the same BYO Google flow locally.

Download the desktop alpha

The SkyTwin desktop alpha release is usable software, not only the fictional demo. Pick the installer for your operating system:

macOS · Apple Silicon

Open the current release. On first launch, right-click SkyTwin, choose Open, then confirm Open.

Windows · x64

Open the current release. If SmartScreen appears, choose More info, then Run anyway.

Linux · x86-64 AppImage

Open the current release and make it executable using your desktop or chmod +x.

Linux · x86-64 packages

Download the current release assets or release notes.

Alpha boundary: these artifacts are unsigned and have no current notarization, clean-machine, or auto-update evidence. This is an early public alpha, not a managed OAuth service or a Google verification/signing claim. This is not a supported installer path for the public beta. Read its release notes and avoid personal data while evaluating it.

Optional real-inbox mode

Connect Gmail in the app or your browser

Start the alpha, then use Connect Gmail in its desktop window for first-account setup. The same five-step local-web wizard is served at http://localhost:3200/#/connect-gmail for a browser that already has a valid SkyTwin session. A fresh browser does not inherit Electron's one-use session-token handoff. You create a Web Application OAuth client in your own Google Cloud project, add the two loopback callback URLs, paste the client ID and secret, and approve the requested scopes. The worker can then ingest real Gmail and Calendar signals.

This is advanced alpha functionality, not a managed SkyTwin OAuth service. Start with a test account: the client secret and newly authorized tokens are stored without app-level encryption in the alpha's configured local database, Google testing-mode grants can expire after seven days, and supported Gmail or Calendar mutation is not part of this capability claim.

Follow the exact Gmail setup guide →

Run a reviewed source checkout

The source installer is a convenience route for its own moving main checkout. To inspect a specific source revision, start that checkout directly instead. This keeps the executable tree and the revision you reviewed the same.

Prerequisites: install Node.js >=20.19.4, Corepack, pnpm, Git, and standard build tools for your operating system before using the manual checkout commands. The one-line installer below can provision supported prerequisites; the reviewed-checkout path assumes they already exist.

git clone https://github.com/jayzalowitz/skytwin.git
cd skytwin
git checkout <reviewed-commit>
pnpm install
./bin/skytwin-db install
./bin/skytwin-db start
./bin/skytwin-db ensure-db
cp .env.example .env
pnpm db:migrate
pnpm db:seed
pnpm build --concurrency=1
pnpm dev

For an extracted, exact-commit source archive rather than a Git checkout, use SKYTWIN_SOURCE_ARCHIVE=true ./install.sh from the extracted directory. The one-line convenience form uses moving main and creates or updates its own checkout: curl -fsSL https://raw.githubusercontent.com/jayzalowitz/skytwin/main/install.sh | bash. Use it only when evaluating that moving source route, not when you need to run the revision you reviewed. Do not use either route on a machine where you cannot review or permit those local changes.

What starts locally

Dashboard and API

The installer starts the local dashboard, API, worker, and CockroachDB-backed development environment. Health endpoints are documented in operations.md.

Models are not silently downloaded

Managed local-model setup is a separate user action. A compatible runtime is required; if it is absent, model-backed reasoning remains unavailable rather than falling through to a hosted provider.

Real accounts are explicit

Current source defaults to the isolated fictional-data sample. Advanced operators can set SKYTWIN_GOOGLE_CONNECTION_MODE=experimental before starting source services to enable the retained BYO Google route. Authorization happens in a normal browser and returns to the local dashboard at http://localhost:3200; Electron is not required. The current alpha exposes its Gmail wizard directly in its window and serves the same route to an already authenticated local browser; use the desktop window for first-account bootstrap.

Network boundaries remain explicit

Connected services, model downloads, configured hosted providers, and adapters can use the network. Read Privacy before configuring any of them.

Evaluate before you connect data

Read the fictional-data demo and use it to inspect approval/explanation behavior.
Read the agent guide if you plan to expose the MCP surface to another agent.
Review the privacy policy and inference boundary before adding a provider or account.
Use the dashboard controls to keep autonomy at the lowest useful level; do not treat an LLM suggestion as authorization.

Release boundary: Signing, notarization, clean-machine evidence, and supported-installer validation remain release gates. See the machine-checked beta claim ledger.