Skip to content

Applications

Applications are the places people actually use ThinkWork. The platform primitives under Components explain how work is represented; the applications are where end users talk with agents, operators configure tenants, and developers deploy or inspect a stack.

ThinkWork has four primary application surfaces. Desktop and Mobile are for end users doing work with agents. Admin is the tenant control plane for operators and agent authors. CLI is the scriptable deployment and operations surface for teams that run ThinkWork in their own AWS account.

ApplicationPrimary audienceMain jobStart here
Desktop AppEnd usersInstalled macOS Spaces app for daily thread, agent, and artifact workDesktop App
Mobile AppEnd usersOn-the-go chat, external tasks, personal integrations, and push notificationsMobile App
Admin Web AppOperators and agent authorsTenant configuration, agent authoring, Spaces, controls, analytics, and MemoryAdmin Web App
CLIOperators and developersDeploy, inspect, and operate ThinkWork stacks from scripts or a terminalCLI Overview

Desktop App

A dedicated macOS app for ThinkWork Spaces: threads, agent chat, generated artifacts, side panels, and command composer in an installed window.

Mobile App

The end-user iOS client for chat, review, external tasks, personal integrations, MCP Connect, and push notifications.

Admin Web App

The operator control plane for tenant configuration, agent authoring, Spaces, Skills, Memory, guardrails, analytics, and settings.

CLI

The thinkwork-cli package for deployment, stack inspection, API-side operations, and automation-friendly management commands.

Start with Desktop App when you want the installed end-user experience. Start with Mobile App when the work happens through notifications, tasks, personal integrations, or a phone. Start with Admin Web App when you are configuring the tenant itself. Start with CLI when the question is deployment, scripting, or stack operations.

For the platform model underneath these apps, read Threads, Spaces, and Agents.

  • Architecture — how the applications fit into the AWS-native deployment
  • Threads — the durable work record shared by the apps
  • Spaces — contextual workrooms used by Desktop, Mobile, and Admin
  • React Native SDK — the SDK behind the mobile client