OpenWorker
SourceDownload

AI that works from your computer.

OpenWorker runs on your computer and works across the apps, files, and accounts you choose. Bring your own model and API key, ask for a finished result, and decide which tools it can use and which actions need your approval.

Download for MacDownload for WindowsComing soon
  • Open source from end to end
  • Your model. Your API key.
  • Local by default. Private by design.
Tomorrow's Acme renewalOpenWorker · your model
Tomorrow 10am with Acme—pull what I need for the renewal call.
7 steps
OpenWorker
They're happy—and might buy more seats

Usage up 46% this quarter. The login bug they filed is closed. Finance still has 18 unused seats—easy upsell if the call goes well.

  • Open with: you're saving ~12 hours/week
  • Ask about trying reports in August
Send Maya (their ops lead) a short recap email?Approval required → EmailApproveNot now
Results /acme-renewal-notes.html
Acme · Renewal notesReady for you
They're happy—and might buy more seats
46%usage this quarter
12 hsaved each week
18open seats left

Keep the plan as-is; float the 18 open seats if they're warm.

Describe what you need…+Needs approvalChoose model
Sales1 / 4
Bring your own stack

Your models. Your keys. Your tools.

Connect OpenWorker to cloud, open-weight, or fully local models using API keys you own. Add only the apps each workflow needs, and change providers without changing how you work.

Model providersYour account · your billing
OpenAIAnthropicGeminiZ.AI · GLMDeepSeekKimiMiniMaxQwenxAIMistralTogether AIFireworksOllama
Everyday toolsOnly the access each workflow needs
SlackOutlookGmailGoogle CalendarNotionHubSpotGitHubAttioGoogle DriveJiraLinearAsanaDropboxBox···More
How control stays yours

Set the goal. Keep the final say.

You choose the model, decide which tools it can reach, and define where approval is required. OpenWorker coordinates the steps on your computer and returns work that is ready to review or use.

1

Select the right model

Bring a cloud API key, choose an open-weight provider, or run with Ollama locally. Use the model that fits the task and change it when you want.

No model lock-in
2

Grant only the access needed

Connect the specific apps, accounts, and folders a workflow requires. Your credentials stay in the local secret store on your device.

Your tools · your permissions
3

Review and release the work

OpenWorker prepares the brief, update, file, or action. Anything consequential waits for your approval before it moves forward.

You approve important actions
A starting point, not a limit

Begin with a workflow. Make it yours.

Start from a practical role, then choose its model, tools, access, and approval rules. OpenWorker adapts to the way your team already operates.

Sales

Builds account context, surfaces expansion signals, and prepares follow-ups for review.

Connected to
HubSpot · Email · Calendar
Waits for approval
before messages or updates go out

Executive Assistant

Organizes the calendar, turns inbox threads into decisions, and protects time for priority work.

Connected to
Email · Calendar · Slack
Waits for approval
before replies or schedule changes

Marketing

Combines campaign signals, explains what changed, and assembles the next report.

Connected to
HubSpot · GA4 (soon) · Slack
Waits for approval
before publishing or sharing

Ops On-call

Connects alerts to recent changes, runbooks, and evidence so responders can act faster.

Connected to
Slack · PagerDuty (soon) · GitHub (soon)
Waits for approval
before commands or production changes
Automation with boundaries

Work can begin before you ask.

Choose the event that starts a workflow and the actions that still need approval. OpenWorker can prepare the next step without taking control away from you.

Slack mentionBuild the incident picture

Collect the alert context, recent changes, and relevant runbook steps.

Incoming emailTurn the request into a draft

Find the supporting details and prepare a response for approval.

Your scheduleHave the update ready

Assemble the latest numbers before the meeting begins.

FAQ

Your stack, your rules.

What do I pay OpenWorker for?

Nothing for the app itself—OpenWorker is open source. Use your own API key for OpenAI, Anthropic, Google, or another supported provider, or run a local model with Ollama. Any model usage is billed directly by the provider you choose.

Where are API keys and connection tokens stored?

They stay on your device in OpenWorker's local secret store. If you use the optional cloud account for an OAuth connection, it only coordinates the sign-in handshake; the resulting token goes to your computer and is not retained in the cloud.

How much can OpenWorker do on its own?

That is up to you. You decide what it can access and how independently it can act. Consequential steps such as sending email, posting to Slack, or running a command can be held for approval in the app or from Slack.

Can I use it without an OpenWorker account?

Yes. The core experience works while signed out with the API keys and tokens you provide. A free account adds one-click connections for tools such as Slack when the vendor requires OpenWorker to manage the sign-in flow.

Am I tied to one model provider?

No. Use OpenAI, Anthropic, or Google with your own API keys; choose open-weight models such as Kimi, GLM, and DeepSeek through supported providers; or run locally with Ollama. You can select a model for each task and switch during a conversation.

Keep the choice

Run your first workflow, on your terms.

Open source, local-first, and ready to use with the model and tools you already trust.

Download OpenWorker for MacExplore the source on GitHub
OpenWorker — AI that works from your computer