outworked

---

---

---

What's New

v0.4.3 — Better bg handling for scheduled tasks.

v0.4.2 — Added browse:type for better browser handling.

v0.4.1 — Pop-out chat windows, fixed asset pack zip import and spaces in directory paths, fixed custom sprite loading.

v0.4.0 — Asset packs system: custom sprites, furniture, backgrounds, and fonts. Multi-pack support with fallthrough. Music player now plays user-added tracks.

v0.3.1 — Slack channel support, triggers UI, improved MCP server wiring, better channel reliability.

v0.3.0 — SQLite storage, iMessage channels, scheduled triggers, skills system, MCP server integration.

See the full Version History below.

---

How It Works

1. Hire agents — Give each one a name, role, personality, model, and sprite
2. Describe a goal — Write what you want in plain English; the orchestrator breaks it into subtasks and routes them to the right agents automatically
3. Watch them work — Agents walk to their desks, write code, interact with the web, send messages, run scheduled jobs — all visible in the office
4. Ship it — Just let your agents handle the whole workflow end to end

---

Example Workflows

These are real things you can do today:

"Build me a landing page and send it to my cofounder"

You type one sentence. Here's what happens:

1. The orchestrator breaks it into subtasks and assigns them across your team
2. Frontend Dev scaffolds the site, writes the HTML/CSS/JS, and starts a local server
3. Designer reviews the page in the built-in browser, takes a screenshot, and asks Frontend Dev to tweak the spacing
4. Frontend Dev makes the fix, then runs tunnel_start to get a public URL
5. Frontend Dev calls send_message to text the link to your cofounder on iMessage

You watched the whole thing happen at the office. You are wowed. Your cofounder gives you more equity. Total prompts from you: 1.

"Every morning at 9am, check our open PRs and text me a summary"

1. You tell your Ops Agent to set up a daily task
2. The agent creates a scheduled trigger with a cron expression (0 9 * * *)
3. Every morning, the agent wakes up, queries the GitHub MCP server for open PRs, writes a summary, and sends it to you via iMessage
4. You read it on your phone over coffee

No scripts to maintain. No GitHub Actions to debug. Just an agent with a schedule.

"Research these three competitor products and write up a comparison"

1. The orchestrator assigns a Researcher agent to each competitor — all three run in parallel
2. Each agent uses the built-in browser to navigate the competitor's site, read docs, take screenshots, and extract pricing
3. A Writer agent collects all three findings, writes a structured comparison doc, and commits it to your repo
4. The Writer asks if you want it sent to Slack — you approve, and it posts to #product

Three agents working simultaneously, finishing in minutes what would take you hours.

"Triage the 12 new GitHub issues from last night"

1. Project Manager agent pulls all new issues via the GitHub MCP server
2. It reads each one, labels by priority and type, assigns to the right team member, and adds a first response comment
3. For any bug it can reproduce, it assigns a Backend Engineer agent to investigate and open a draft PR with a fix
4. You get a Slack summary of what was triaged, what's in progress, and what needs your attention

---

Capabilities

Write and ship code — Build features, fix bugs, open PRs, review each other's work, run tests, and deploy — across multiple repos at once.

Browse the web — Research docs, scrape pages, fill out forms, take screenshots, and bring findings back to the team via the built-in browser.

Send and receive messages — Reply to customers on Slack, text you a summary on iMessage, or monitor a channel and trigger tasks when someone says the magic word.

Run on a schedule — Daily standups, weekly reports, hourly health checks, one-off reminders. Set a cron and let an agent handle it while you sleep.

Query databases — Connect a PostgreSQL MCP server and let agents run queries, generate reports, or investigate production issues without you writing SQL.

Manage projects — Create and triage GitHub issues, update Linear tickets, post status updates to Slack — agents can own the workflow, not just the code.

Anything you can plug in — Every MCP server you add gives agents new capabilities. Connect your internal APIs, monitoring dashboards, CMS, or anything with a tool interface. If it exists as an MCP server, your agents can use it.

---

Features

• Pixel Office — A Phaser-powered world where your agents walk, sit at desks, and collaborate in real time
• Build a Team — Give each agent a name, role, personality, model, and sprite. Mix Claude Opus for hard problems with Sonnet for fast ones
• Auto-Orchestration — Describe a goal; the router breaks it into tasks and assigns them to the right agents
• Multi-Agent Collaboration — Agents talk to each other via [ASK:AgentName] and a shared message bus
• Full Claude Code Power — Every agent gets full tool access (Bash, Edit, Read, etc.) with persistent sessions
• MCP Server Support — Connect agents to external tools and services via the Model Context Protocol
• Messaging Channels — Connect iMessage and Slack so agents can send and receive messages in real conversations
• Built-in Browser — Full Chromium browser for agents to navigate, click, fill forms, and take screenshots
• Built-in Tunneling — Expose local servers to the internet via Cloudflare tunnels with a single tool call
• Triggers & Scheduling — Fire off agent tasks on a schedule (cron, interval, one-time) or in response to incoming messages
• Skills System — Extend agents with plug-in SKILL.md files that define tools, auth, and instructions
• SQLite Storage — Persistent local database for skills, settings, channels, and message history
• Permission Gates — Real-time approval modal for sensitive tool calls
• Live Chat — Markdown-rendered conversations with syntax-highlighted code blocks and diffs. Pop out any chat into its own window for side-by-side work
• Built-in Git — View status, staged changes, branches, and create PRs without leaving the app
• File Browser — Live-updating workspace tree that syncs as agents edit files
• Cost Dashboard — Track tokens and spend per agent, session, and day
• Background Mode — Minimize and let agents keep working. Tray icon keeps you updated
• Parallel Processing — Multiple agents tackle subtasks simultaneously
• Desktop Notifications — Get pinged when tasks finish or agents need approval
• Asset Packs — Customize your office with custom sprites, furniture, backgrounds, and fonts — drop a folder and go
• Original Soundtrack — Because every office needs a vibe

---

Supported Models

Provider	Models
Anthropic	Any model via Claude Code.

Each agent can run a different model — pair a fast model for simple tasks with a powerful one for complex work.

---

Get Started in 2 Minutes

1. Install

Homebrew (recommended)

brew tap outworked/tap
brew install --cask outworked

Manual download

Grab the latest .dmg from the releases page and drag to Applications.

2. Prerequisites

• Claude Code installed and authenticated

3. Launch and Hire Your First Agent

On first launch, the onboarding modal walks you through picking a workspace and creating your first agent. You'll be watching pixel employees do stuff in under two minutes.

Build from Source

This will start up a development instance of Outworked. To build a distributable, use npm run electron:build instead of npm run electron:dev

git clone https://github.com/outworked/outworked.git
cd outworked
npm install
npm run electron:dev

---

Scripts

Command	Description
npm run dev	Start Vite dev server (browser only, no Electron) for testing only. Won't work correctly.
npm run electron:dev	Build and launch the full Electron app in dev mode
npm run electron:build	Package distributable (dmg/zip on macOS, exe on Windows, AppImage on Linux)

---

Tech Stack

Layer	Technology
Desktop	Electron
Frontend	React 19 + TypeScript + Tailwind CSS
Build	Vite
Graphics	Phaser 3
Storage	SQLite (better-sqlite3)
AI	Claude Code SDK

---

Project Structure