Player profile
Tempest
An Apache-2.0 Tauri-based ADE (Agentic Development Environment) that runs CLI coding agents with 64% fewer tokens via an embedded xterm.js terminal.
Profile
Where it fits
Tempest is a Tauri-based desktop ADE for running CLI coding agents such as Claude Code with dramatically reduced token usage. Its embedded xterm.js terminal gives agents a real shell surface while token intelligence trims context overhead by 64%.
It belongs in Open Orchestrators because it frames coding-agent work as a first-class native desktop operating surface: isolated database branches per agent session, multi-agent session management, and a custom frameless window built specifically for agentic engineering workflows.
Builder web analytics
Measure projects built with Tempest
Tempest runs coding agents with fewer tokens and isolated workspaces. Agent Analytics gives those agents user-facing outcome data after a Tempest-built change ships.
Install Agent Analytics on the project surface Tempest agents help ship. The token intelligence and DB isolation features are orthogonal to analytics; Agent Analytics measures user-facing outcomes after the change lands.
First loop to measure
- a builder uses Tempest to run a coding agent session and ship a page, docs update, onboarding change, or product surface
- the changed surface reports visits, sources, CTA clicks, signup, activation, retention, funnels, and experiment events to Agent Analytics
- a follow-up Tempest agent session fetches the Agent Analytics results and compares the shipped path with the prior period
- the builder decides what to improve next from user behavior, closing the agentic development loop
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including Tempest-built page, traffic source, CTA click, signup, activation event, funnel step, experiment, or shipped agent session. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which Tempest-built page, traffic source, CTA click, signup, activation event, funnel step, experiment, or shipped agent session moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.