Tines Desktop
Open source desktop companion for Tines

Browse. Debug. Investigate.

Tines Desktop is an unofficial Electron app for exploring stories in a safer read-only flow, tracing execution visually, looking up old incidents by Event ID or Story Run GUID, and saving local investigations with screenshots and evidence.

Tines Desktop story canvas
The app is optimized for understanding story structure and operational state without immediately dropping into mutation-capable editing.

Why this project exists

Tines is powerful, but day-to-day operational work often needs a different shape than the browser alone: safe inspection, focused debugging, incident-driven lookup, and a way to preserve findings locally. Tines Desktop aims to make that workflow faster and easier to reason about.

Read-only story browsing

Open stories in a browse-first canvas with local-only layout, zoom, search, and export tools.

Forensic lookup

Start from an Event ID or Story Run GUID and resolve story, action, run, and artifact context.

Visual debug trace

Inspect execution history and supported health signals across the story graph.

Safety map

Review blast radius, risky nodes, and where bad data may be re-emitted or propagated downstream.

Investigations

Save local investigative sessions with findings, screenshots, run context, and evidence artifacts.

Separated editor

Keep routine investigation safe while isolating mutation-capable behavior in a clearly marked editor surface.

Feature highlights

These are some of the strongest workflows in the current alpha. The visual language is intentionally bold and operational: readable graphs, explicit risk cues, and a clear separation between inspection and editing.

What to know before using it

Unofficial and unsupported

Tines Desktop is an open source side project and is not an official Tines product. It is not supported by Tines. You should treat it as an alpha-quality companion app.

Editor warning

The editor surface exists, but it is not the strongest part of the product today. The recommended workflow is still the read-only investigation path unless you explicitly want to test editor behavior.

Connection profile security

Saved profiles use Electron safeStorage when the host OS supports it, which is the normal expectation on macOS and Windows. Edge-case environments such as stripped-down Linux systems are where that assumption is weaker.

Debugger API limitation

The app is good at reconstructing execution and supported health signals, but it does not always get the exact action-log detail shown in the Tines web UI. Use the desktop debugger as a strong operational view, not perfect browser parity.

Quick start

The fastest path is to install a release build, create a connection profile, add your Tines tenant URL and API key, and start browsing stories immediately.

1. Download the latest release from GitHub
2. Launch Tines Desktop
3. Create a connection profile
4. Enter your tenant URL and Tines API key
5. Open Dashboard and start exploring stories

Get the latest builds from GitHub Releases.

Looking for a deeper walkthrough? Start with the full user guide.