StatsKey Desktop

Intelligence that finishes the work.

Give StatsKey the outcome. Follow its progress in plain English, steer it without starting over, then review the files, checks, and final handoff.

Mac 0.21.6 · signed and Apple notarized · Windows 0.19.1 preview

Search experience · StatsKey workspace Complete
Make the search field usable, verify it, and tell me exactly what changed.

I found the layout issue.

I’m widening the field, then I’ll run the focused verification.

  • Read the search interface
  • Updated the field layout
  • Build and verification passed
DoneVerified

The search field now stays usable in a narrow window and expands when more room is available.

Message StatsKey at any point…Send
Less ceremony. More completion.

You should never wonder what it is doing.

StatsKey turns autonomous work into a conversation you can follow, influence, and review.

1

Stays on the job

It works through implementation and verification before handing back control.

2

Shows real progress

Plain-language updates explain the current action and the next concrete step.

3

Steer it live

Send a correction while it works. Queue a follow-up without breaking the run.

4

Hands back proof

Review linked files, changed lines, checks, and the final result in one place.

Parallel when useful. Quiet when not.

Separate tasks can move at once. Overlapping edits and builds are coordinated. Simple questions stay simple.

Your context, only when invited.

Projects, email, calendar, and health context stay bounded. Personal context is off in workspaces unless you enable it.

Capability catalog · Mac 0.21.6

What StatsKey can do today.

A maintained, plain-language list of the current Mac app’s capabilities. The Windows preview remains on 0.19.1. Each release updates this catalog and the version history below.

01

Choose how StatsKey helps

Start simply, then expose technical controls only when you need them.

  • Automatic chooses the safest capable approach from your request.
  • Ask researches and explains without changing anything.
  • Plan creates an editable step-by-step plan without changing anything.
  • Fix diagnoses a problem, makes the repair, and verifies the result.
  • Execute completes the task, makes the needed changes, and verifies them.
  • Advanced settings keep model, context, reasoning, and action controls available.
02

Work in real projects

Use the same local files and project structure you already trust.

  • Open local and multi-root workspaces with files, tabs, split editors, and persistent layouts.
  • Read, search, create, edit, rename, and delete files inside the approved workspace.
  • Use encrypted local indexing with ignored-file and secret-file exclusions.
  • Review workspace changes, linked files, checkpoints, and saved results in one place.
  • Open GitHub-backed browser workspaces with explicit remote diff review.
03

Run and verify the work

Implementation and proof stay connected.

  • Run terminal commands, builds, tests, and focused verification in the bound workspace.
  • Inspect Git status and diffs, stage or unstage changes, and approve commits.
  • Generate and preview selection-aware inline edits before applying them.
  • Keep long-running tool output visible and synthesize a final verified handoff.
  • Restore checkpoints when a reviewed change needs to be reversed.
04

Stay in control while it works

You can follow, redirect, pause, and resume without starting over.

  • See the current action, elapsed work, completed steps, and next concrete step.
  • Send corrections, queue follow-ups, reorder queued work, or interrupt with a priority message.
  • Keep conversations and active work recoverable when tabs are closed or switched.
  • Run up to two independent top-level tasks at once while conflicting edits remain coordinated.
  • Create isolated task workspaces from a clean committed baseline.
05

Test what people actually use

Verification can extend beyond source files.

  • Open isolated browser tabs, inspect bounded page content, click, type non-secret text, and capture screenshots.
  • Discover and launch approved local applications.
  • Discover, boot, inspect, and interact with iOS Simulators and Android emulators.
  • Install and launch mobile builds, capture device screenshots, and inspect process logs.
  • Keep browser and device evidence tied to the conversation that requested it.
06

Use the right Intelligence

Choose a managed route or connect your own provider.

  • Select a model, reasoning effort, context size, and managed or direct-provider route.
  • Store supported provider keys in encrypted local storage.
  • Stream responses, cancel work, and use bounded subagents for independent investigation.
  • Connect approved MCP tools over local or remote transports with exact-argument review.
  • Attach files and inspect how much context a task is using.
07

Connect personal tools only when invited

Work and personal context remain separate by default.

  • Work conversations cannot read health, calendar, inbox, or personal memory unless you explicitly include allowed context.
  • Personal conversations do not receive project files, terminal, Git, MCP, or browser automation.
  • Connect Google Calendar or Gmail with separately chosen read, create, and send capabilities.
  • Review the exact email or calendar event before an external action is completed.
  • Bring optional health context into an approved workspace without silently enabling other personal sources.
08

Turn plans into durable artifacts

Plans remain editable, reviewable, and connected to implementation.

  • Create local planning canvases with checklists, revisions, and bounded flow diagrams.
  • Refine a plan conversationally without losing its prior revisions.
  • Save a plan into the workspace with conflict checks.
  • Fork a plan without changing the original.
  • Start implementation from an immutable plan handoff.
09

Customize the workspace

Shape StatsKey through the same review boundary as project work.

  • Discover workspace rules, skills, hooks, MCP configuration, and connected tools in one Customize surface.
  • Open StatsKey’s own source from Settings and describe the interface or workflow change you want.
  • Review and verify customization changes before they become part of a release.
  • Use workspace hooks for prompts, responses, file reads, mutations, terminal commands, and MCP actions.
10

Review and protect changes

Capability does not remove the approval boundary.

  • Choose Review each, Auto-review, or Run everything for local actions.
  • Keep file writes and commands contained to the approved workspace with symlink and external-file protection.
  • Require explicit approval for deletion, external actions, commits, MCP calls, and configured hooks.
  • Block password fields, unsafe destinations, popups, downloads, and hidden permissions in controlled browsing.
  • Receive signed, notarized macOS updates through immutable architecture-specific feeds.

Updated Machine-readable catalog

What’s new

A running record, in plain language.

A concise, product-level history of the improvements that matter day to day.

Version 0.21.6 · macOS

Public boundary correction

A focused Mac correction removes a residual private-machine command path from the public package and strengthens the checks that guard future releases.

  • The public Mac package no longer contains the dormant Remote Access execution path that remained in 0.21.5.
  • Compiled assets are now checked for Remote Access, MacRemote, Oil Data, remote-command, and private-machine markers before publishing.
  • The clearer mode chooser and reviewable customization workflow from 0.21.5 are unchanged.
Mac 0.21.6 · Windows 0.19.1

Start with the outcome.

Bring a project. Tell StatsKey what finished looks like. Stay in the conversation.

On Mac, open the DMG and drag StatsKey to Applications. The app and disk image are signed and notarized by Apple. On Windows, SmartScreen may require More info → Run anyway while the Windows preview is unsigned.