stickyinc · v0.5.2 · the subscription-mode release

Your chats evaporate.
This sticks.

A floating pane plus an MCP server. The things you decide in a chat — call the dentist, email Sarah, schedule the review — don't vanish when the tab closes. They land on the side of your screen and wait until you tick them off.

Download Read the idea

Free. Open source. MIT. BYO key. Works with Claude, OpenRouter, OpenAI, or any OpenAI-compatible endpoint. No backend, ever.

Chats are cheap.
The commitment graph is what compounds.

┌──────────────────────────┐ ┌──────────────────────────┐ │ user ▸ call the │ MCP │ ☐ call the dentist │ │ dentist friday │ ─────▶ │ ☐ email Sarah │ │ claude ▸ noted, adding. │ tool │ ☑ ship v0.5 │ └──────────────────────────┘ │ ☐ make it stick │ │ └──────────────────────────┘ the chat the pane evaporates at close lives in ~/.stickyinc forever

Every other AI overlay on the market follows the same shape — summon, ask, dismiss. The model is a disposable oracle; you are the durable storage. You close the tab and within an hour the answer has evaporated from your brain.

StickyInc is the inverse. Chats are ephemeral; the graph of commitments you build from them over months — the promises, deadlines, quiet todos you let slip into conversation — is the part that actually compounds. Nobody was storing it. StickyInc is the canvas it lands on.

Swap Claude for GPT tomorrow. Your pane is still there.

Three small moves.

Claude writes it.

In any Claude Code or Claude Desktop session, say "I need to call the dentist Friday." Claude calls StickyInc's MCP. A new checkbox appears in your pane before you finish reading its reply.

You tick it.

Hover the strip on the right edge of your screen. The pane slides out. Click to complete — the task strikes through, then drops into a quiet archive for tomorrow-you. The line Claude sees next turn says "user completed: call the dentist."

Calendar gets it.

Dated items forward to Google Calendar through Claude's own connector. StickyInc doesn't run its own OAuth flow — one less thing to set up, one less place your tokens live.

Two processes.
One SQLite file.

┌──────────────────┐ MCP stdio ┌──────────────────┐ │ Claude Desktop │ ───tool call──▶ │ StickyInc MCP │ │ Claude Code │ │ (Node, stdio) │ │ any MCP host │ └────────┬─────────┘ └──────────────────┘ │ SQL ▼ ┌─────────────────────────┐ │ ~/.stickyinc/tasks.db │ │ (SQLite, yours) │ └─────────────┬───────────┘ │ notify-rs watcher ▼ ┌────────────────────┐ │ Pane (Tauri) │ │ edge-strip, always │ │ on top, translucent│ └────────────────────┘

Claude never talks to the pane directly. They share state through SQLite — one source of truth, nothing to sync, no IPC to break. The MCP server ships as a stdio binary; the pane is a Tauri app under 1 MB of Rust. Both read and write the same tasks.db.

Pick your platform.
One click. One minute of setup.

Every tagged release ships binaries for macOS, Windows, and Linux — all built in CI from this repo, all open source. Builds are currently ad-hoc signed; notarized installers arrive in v0.6 (see SIGNING.md).

macOS Apple Silicon · arm64

StickyInc_0.5.2_aarch64.dmg

Download .dmg

drag to /Applications · Gatekeeper will warn on first open

Windows x64 · installer

StickyInc_0.5.2_x64-setup.exe

Download .exe

NSIS installer · SmartScreen warns until v0.6 signing

Windows x64 · MSI

StickyInc_0.5.2_x64_en-US.msi

Download .msi

for group-policy deployment

Linux Debian · Ubuntu · x86_64

StickyInc_0.5.2_amd64.deb

Download .deb

sudo dpkg -i StickyInc_0.5.2_amd64.deb

Linux Fedora · RHEL · x86_64

StickyInc-0.5.2-1.x86_64.rpm

Download .rpm

sudo rpm -i StickyInc-0.5.2-1.x86_64.rpm

Linux portable · any distro

StickyInc_0.5.2_amd64.AppImage

Download .AppImage

chmod +x and run — no install needed

From source mac · win · linux

git clone + pnpm tauri:dev

Dev setup →

needs Rust + Node 20+ · hack on the pane live

What StickyInc will never do.

no backend. your chats never hit our servers, because we don't have any. you bring your own LLM key; we bring a binary.

no chat UI. Claude Desktop and Claude Code already exist. StickyInc is the canvas they write to, not another window to switch between.

no cloud sync. your commitments live in ~/.stickyinc/tasks.db. sync it with iCloud, Dropbox, Syncthing, or don't — it's your file.

no OAuth flow we don't need. we defer calendar writes to Claude's own Google connector. one less place your tokens live.