Agentic Workspace Environment · macOS

Your agents workin the same roomas you.

macOSTauri 2 · RustMITv0.1.0

Spark is a desktop workspace built around tabs. Terminals, files, PDFs, tables and agents live side by side in one window — and share the same objects.

Spark window with three tiles: a Codex terminal, a data table of WMT 2014 BLEU scores for Attention Is All You Need, its bar chart, and the paper itself.

AWE

An agentic workspace, not another chat window.

Most agent tools put the conversation in the middle and the work at the edges. Spark does the opposite: the workspace is the surface, and the agent plugs into it.

One tab, many tiles

A terminal, a PDF, a table and a chart, split and grouped. Each tile keeps its own state, and a terminal keeps its session.

Shared objects

An agent opens a tile, reads its declared state and calls typed actions. It never scrapes the screen or fakes a click.

Local by default

The MCP bridge is a Unix socket with 0600 permissions. No network port, no account, no cloud relay.

Product

What is already in the box.

Six tiles, one workspace. Everything below ships in the app today, not in a roadmap.

01

Terminal

A real PTY session per tile. It survives layout changes and tab switches, and restarts fresh after a launch.

02

Explorer

A folder tree that opens a file in Markdown or a shell in the right directory, for you and for agents.

03

Markdown

Editor and preview over the same document, with line-addressed actions so an agent edits precisely.

04

PDF

An https link is fetched and cached. The content stays out of MCP: agents only see the title and page count.

05

Data

Typed tables — text, number, date — up to 2,000 rows and 32 columns, with charts bound to the table itself.

06

OpenAlex

Search by topic, author or DOI, read a work's fields, and open its free PDF beside your notes.

MCP

The agents you already use, in the workspace you already have.

Spark speaks the Model Context Protocol over a local socket. Fifteen tools, one server, and a bridge that is already in the bundle.

Claude Code
Codex
Cursor
Gemini CLI
OpenCode
Mistral Vibe
Any MCP client works.These six are configured by Spark in one click. Any other client only needs the bridge path shown below — no plugin, no port to open.

How an agent actually works here

No screenshot parsing, no computer-use heuristics. The agent calls the app, and the app answers with references and summaries.

Spark holds the server.

The MCP server lives inside the app, behind a Unix socket with 0600 permissions. The bundled spark-mcp binary relays a client's stdio to it.

Your agent reads the tab.

spark_brief returns the tab, its tiles and their surfaces. spark_tile_read adds the data and the actions that tile accepts right now.

It acts on real objects.

spark_tile_open creates a tile, spark_tile_call runs a typed action, spark_tile_move and spark_tile_resize arrange the tab.

You keep the last word.

Any action that changes data is flagged mutates and executed; asking for confirmation is the client's job. Tabs an agent opens stay in the background.

Interaction

Arrange the work by hand, undo it like text.

The layout is a direct manipulation surface. No presets, no layout dialog — just the gesture you would expect, and a history that covers agents too.

Drag → edgeSplitDrop a tab on a border and the tab divides in that direction.
Drag → centerGroupDrop it in the middle and it joins the tile as a tab, keeping both alive.
Drag separatorResizeBoth neighbours resize at once. The split ratio is persisted per tab.
⌘KPaletteEvery command, tile and pinned extension action, from the keyboard.
⌘Z · ⇧⌘ZUndo the layoutMoves and resizes, including the ones an agent made. Never the content.
Side · Stack · TilingThree modesSwitch the arrangement without recreating a tab or killing a terminal session.

The same moves exist as two MCP tools: spark_tile_move and spark_tile_resize.

Extensions

Extensions add tiles.

The app is built from tiles: terminal, Markdown, PDF, data, OpenAlex. The Store adds the rest.

01

Browse

The Store lists what is available, what is installed, and which registry each one comes from.

02

Install

One click. The zip is checked before extraction; a failure leaves the previous version in place.

03

Import

A local folder, in developer mode. Nothing updates on its own.

Unsigned and unsandboxed

Imported extensions run in the main window with the app's privileges, and no signature is verified today. Spark treats them as code you chose to trust — install what you would run from a terminal.

The SDK, in detail

Status

What works, and what does not, in v0.1.0.

A short honest list beats a feature grid. This is the state of the repository today.

Platform
macOS for now, built locally. The PTY layer also targets Linux; Windows is not supported yet — the MCP bridge relies on a Unix socket.
Builds
Signed: no. Notarised: no. Builds are unsigned, so macOS asks you to confirm on first open.
Downloads
No release artefact yet. You build from source with Node, Rust and the Xcode command line tools.
Updates
No update channel. Pull the repository and rebuild.
Extensions
Imported packages are unsandboxed and signatures are not verified. Registry sources are capped at 20.
Licence
Code under MIT. The name and the logo are covered by a separate trademark policy. No CLA — a DCO sign-off.
Telemetry
None in the app. This site uses Vercel Web Analytics, without cookies.

Start

Clone it, run it, break it.

The only installation path today is the source. It takes Node 22.18+, Rust and the Xcode command line tools.

  1. Clone and install
    git clone https://github.com/nnnnnzo/sparkawe.git
    cd sparkawe && npm install
  2. Build the MCP bridge
    npm run sidecar
  3. Run the app
    npm run tauri -- dev