Skip to content
Safa
Download for Mac

Workflows

One request, in your own words. Agents open real pages, work in plain sight and leave you something to keep. Here is how that looks for eight kinds of work.

Travel

A whole trip from one request.

Helpers check flights and stays on several sites at once. You get a plan, day by day, and a task for each booking.

You keep An itinerary, a comparison of stays and a task for every booking.

Plan two weeks in San Francisco for a founder trip in March, flying from London. Stay near SoMa and keep it under $6k.

  1. Helpers compare flights and stays on different sites, each on its own live page.
  2. Prices land in one table, with the total set against your budget.
  3. The itinerary comes back day by day, and one press turns the bookings into tasks.

Buying

Weigh three options, then decide.

Helpers read each product page at the same time. The differences end up in a table and a chart, not in a dozen open tabs.

You keep A comparison table, a chart and a recommendation with its sources.

Compare three 27-inch 4K monitors under $600 for programming, and tell me which one to buy.

  1. Helpers open each product page and its reviews, in plain sight.
  2. Price, size, ports and the complaints that repeat go into one table.
  3. A chart shows where they differ, and a recommendation says which and why.

Research

Read widely, keep what matters.

For students and analysts: many pages read at once, and findings that stay with their sources.

You keep A summary, a chart and a reading list.

Find recent studies on remote work and productivity, summarise what they found and chart where they disagree.

  1. Helpers read papers and articles, each one a live page.
  2. Findings go into a table, with a chart of where they differ.
  3. Every finding keeps a link to the page it came from.

Job search

Apply with a CV that fits each job.

Grant the folder that holds your CV. It reads the postings and proposes changes, and nothing is saved until you approve.

You keep A tailored CV for each posting and a task for every application.

Read these three job postings, tailor my CV in the Applications folder for each, and keep track of where I apply.

  1. Helpers read each posting and pick out what it asks for.
  2. Reads your CV in the folder you granted and proposes a tailored copy for each posting.
  3. Every application becomes a task, with a day to follow up.

Founders

Research a market in an afternoon.

Send helpers after every source at once, and watch each one work on the real page.

You keep A comparison table and a plan, saved on the canvas.

Compare pricing for the five leading tools in our space and tell me where we should sit.

  1. Helpers open each pricing page in parallel, in plain sight.
  2. Every plan lands in one table, side by side.
  3. A recommendation, written beside the sources it read.

Marketing

From launch notes to launch day.

Point it at your notes and the tabs that matter. It drafts in your voice and shares only when you say so.

You keep Drafts, sources and the tasks to publish them.

Read our launch notes and last month's posts, then draft the announcement and three social posts.

  1. Reads your notes and the tabs you choose to share.
  2. Drafts the announcement and the posts beside their sources.
  3. Shares the drafts in Slack for review, through MCP, when you approve.

Support

Triage the queue before standup.

Connect GitHub and Slack through MCP. It reads what came in and sorts it, and drafts replies you approve before anything is sent.

You keep A triage table and drafted replies, ready to send.

Check our status page and the new GitHub issues, group them by cause, and draft a reply for each in Slack.

  1. Reads the status page, and the new issues on GitHub through MCP.
  2. Issues are sorted into a table by cause and by how urgent they are.
  3. Replies are drafted for Slack, and sent only when you approve them.

Developers

Understand the code, then change it.

Grant a folder and ask in plain words. The agent reads before it writes, and asks before it changes a file.

You keep A map of the system, the new test and a pull request.

Read the payments folder, explain how refunds work, then add a test for partial refunds and run it.

  1. Reads the folder you granted and maps the code on the canvas.
  2. Writes the test, asks before saving it, and runs it.
  3. Opens a pull request through the GitHub CLI you already use.