Skip to main content
Use this path if you want to understand what OpenWork can do before you think about CLI commands or runtime details.

Start with outcomes

OpenWork works best when one worker owns one repeatable outcome. The goal is to make recurring work easier to run, review, and share.

Daily ops summary

Watch incoming work, flag issues, and deliver a morning brief.

Weekly team brief

Roll up wins, blockers, and follow-ups into one update.

Competitor scan

Track launches, pricing changes, and market movement on a schedule.

PR review and triage

Check new pull requests, sort issues, and draft first responses.

Social drafts

Turn changelogs or notes into ready-to-review posts.

Follow-up emails

Draft polished follow-ups from CRM notes, meeting notes, or action items.

Start in the app

The easiest first run is the desktop app.
  • Install OpenWork.
  • Create one worker for one outcome.
  • Run one visible task before you add more automation.

Use the desktop quickstart

Get from install to first worker in minutes.

Keep workers separate

Use one worker per team, client, or domain so work stays predictable.

Share with teammates

One person can set up the worker, then everyone else can join the same flow.
  • Fastest: send OpenWork invite link.
  • Manual: share OpenWork worker URL + Access token.
  • Best practice: keep one worker per team or domain instead of mixing everything together.

See the share flow

Remove copy and paste friction for new teammates.

Add repeatable jobs

Turn good one-off prompts into repeatable workflows.