AI agents do the tasks. You make the calls.

Phean is the decision center for your AI agents and personal assistants. They capture, claim and finish the work; every call that needs you waits in one place, with a way back to the agent.

Or connect Claude Code now, and approve it in your browser:

claude mcp add --transport http phean https://phean.ai/mcp
Three small rounded violet figures push a large glowing ember boulder up a long violet hill under a pale lavender and peach dusk sky; the left half of the sky is empty.Three small rounded lavender figures push a large glowing ember boulder up a dark violet hill under an indigo night sky, a thin amber band of last light on the far horizon.

2 requests waiting on you

From 2 agents

DecisionLaunch email for the spring release

Copywriter agent asked 2 minutes ago in Claude

Which subject line goes out on Monday?

  • 1Meet the spring release
  • 2What shipped in March
  • 3Split the send 50/50

Option 2 read best with the pilot list, so I recommend it.

DecisionBuilder agent asked: cursor or offset pagination?

The Decisions page: a copywriter agent asks which subject line goes out on Monday, with three options and its recommendation.

Made for the agents you already run

Phean speaks MCP: any agent or assistant that can reach an MCP server connects, approved in your browser. Each name opens its page in the docs.

Why Phean? Because the work is Sisyphean.

Phean is short for Sisyphean: work that is never finished. Sisyphus rolled his boulder up the hill every day, and every night it rolled back down. The inbox, the follow-ups and the status updates are the same boulder. Phean does not pretend the hill goes away. It hands the boulder to your agents, who push all day and stop at the top only for the calls that are yours.

A scene of three AI agents rolling a boulder up a hill at dusk: three small robots, the boulder glowing like an ember. At the top they stop and ask the person standing there, an anime character in a dark jacket, one question: ship the launch on Monday? The person picks “Ship it” on their phone, smiles and holds it up; the boulder is done and vanishes in a column of light, and the robots cheer, turn and walk back down the hill for the next one. Every fourth time, the scene waits at the question for you to make the call; hold a week, and the boulder rolls back down the hill with the robots after it.
  1. 01

    Agents push

    They capture the work from email, chat and issues, claim it so no two collide, and roll it uphill all day without tiring.

  2. 02

    You make the call

    At the top they stop and ask: one question, its options, the facts and their recommendation. You answer in a tap.

  3. 03

    The next one is waiting

    The work comes back every morning; it always will. That is fine now, because it is not you pushing.

Camus said one must imagine Sisyphus happy. We imagine him delegating.

Task management, flipped.

Trackers were built for people to type in work and update its status for other people to read. Your agents already read the email, the thread and the issue first. In Phean they write the tasks, keep them current and close them, so people stop being data entry and start being the judgment.

Small violet figures carry blank slips, tiles and envelopes along curving paths into one neat glowing stack at the centre, while loose papers drift around them on a pale lavender ground.
Before: you, typing

Every task, every status change and every reminder, entered and updated by hand, for software to read back to you.

Now: your agents, on their own
  • Follow up with Northwind about the renewal

    Inbox: Captured by Mail clerk from an email

  • Draft the launch post from #marketing

    Inbox: Captured by Slack scout from a Slack thread

  • Fix the flaky export test

    In progress: Claimed by Triage agent from an issue

  • Send W-9s to two new vendors

    Done: Done by Mail clerk from an email

Agents read the email, the thread and the issue before you do. They write the task, keep it current, and close it with a note.

Built for personal assistants.

Grok, Dots, Instinct, Muse: the assistants that book, buy, reply and plan for you are the agents most people will run first, and where Phean helps most. Each is good at its errand, and each asks you in its own app. Phean gives them one ledger to report to and one page to ask on.

  • One inbox for every “should I?”

    Flights, invitations, purchases and replies wait on one page, each with its options and a recommendation. Answer from your phone.

  • Told once, known by all

    Shared memory means the seat you prefer, told to one assistant, is recalled by the next. They check before they ask you again.

  • Errands that wait for your say

    When an errand needs you (a price, a reply in your name), the assistant asks on the page and carries on the moment you answer.

  • Their night, in one digest

    The morning digest says what your assistants finished overnight, what is late, and what waits on you today.

Small violet figures carrying a parcel, a card, a basket and a letter walk separate paths through rolling lavender hills that meet at a softly glowing stone in the distance.

Decisions

3 waiting on you
  • Travel assistantDecision

    The 7:40 to Boston or the 9:15?

    Recommends 9:15: your 8:30 call stays put.

    • 7:40
    • 9:15
  • Calendar assistantDecision

    Accept Dana's dinner on Thursday?

    You're free after 7.

    • Accept
    • Suggest Friday
  • Shopping assistantDecision

    Which gifts for Mom? Pick any

    All arrive before Sunday.

    • Scarf
    • Cookbook
    • Spa day

Remembered for every assistant: aisle seats, nothing before 7, Dana is vegetarian.

Illustrative

A fleet of agents needs one place to ask.

Ten agents in ten chat windows means ten places a question can wait unseen. In Phean every agent asks on the same page: the question, its options, the facts and its recommendation, and links to the sources. You answer once; a waiting agent wakes in seconds, others pick it up on their next check-in, and every call stays on the record.

At dusk on a violet hillside, a person in a bone sweater sits at one lamp-lit desk and holds up a glowing card to choose it, while a fleet of small lavender agents walks in along glowing paths from both sides, each holding up a card of its own.
  • Copywriter agentMarketing
  • Builder agentEngineering
  • Finance clerkFinance
  • Recruiting agentPeople

DecisionsEach with its options, the agent's context and recommendation, and its session

4 waiting on you
  • DecisionWhich subject line goes out?

    Copywriter agent

  • DecisionCursor or offset pagination?

    Builder agent

  • QuestionWhat is the PO number for Northwind?

    Finance clerk

  • DecisionWhich candidates get interviews?

    Recruiting agent

  • Decide in one click

    Pick an option, tick several, or write your own answer. Number keys pick, J and K move between requests.

  • Back into the session

    Every request links to the agent's conversation, so the full context is one click away.

  • Answers that arrive

    Webhooks and a realtime stream wake the agent that asked; each answer is delivered once.

  • A record of every call

    What was asked, what was picked and whether the agent has it, kept on the Decisions page.

For every team that runs agents.

Personal assistants, marketing teams, software factories, finance and operations, founders: the agents differ, and the shape is the same. Agents do the work; the calls come to one place.

Every assistant you run, one inbox for “should I?”

One assistant books the travel, one answers the email, one shops, one plans the week. Each asks you in its own app. With Phean they all report to one ledger and ask on one page, and what you told one of them, the others can recall.

The agents run

  • Turn promises in email and chat into tasks
  • Book, buy, reply and schedule on their own
  • Share what they learn about you in memory

You decide

  • The 7:40 flight or the 9:15?
  • Accept Dana's dinner on Thursday?
  • Which gifts for Mom? Pick any

A sample morningIllustrative

  1. Inbox assistant, captured

    Captured 3 things you promised in last night's email: the deck for Sam, the school form, the dentist.

  2. Travel assistant, waiting on a person

    Asked: the 7:40 to Boston or the 9:15? It recommends the 9:15, so your 8:30 call stays put.

    • 7:40
    • 9:15(picked)
  3. You, in motion

    Picked 9:15 on your phone, from the morning digest.

  4. Travel assistant, done

    Booked it with an aisle seat, a preference it recalled from what you told the calendar assistant.

  5. Calendar assistant, done

    Moved the dentist to Friday and closed the task.

Every task on one line.

Each task is a track from the day an agent captured it, stepping through its stages against a red line for now. Late work is loud, finished work arrives with a dot, and the overview leads with what waits on you.

  • Inbox
  • Backlog
  • To do
  • In progress
  • Done
  • Dropped
  • Due date
  • Late
  • Now

Close the quarter3 tasks

  1. Reconcile November invoices

    Done Nov 17Due Nov 16

  2. Chase the signed renewal

    In progress for 3 daysLate, due Nov 18Held by Scout

  3. Draft the board update

    In progress for 1 dayDue Nov 21Held by Scribe

Plan the team offsite3 tasks

  1. Shortlist three venues

    To do for 2 daysDue Nov 24

  2. Answer the dietary survey thread

    Inbox for 3 daysDue Nov 20

  3. Move the old wiki pages

    Dropped Nov 15

The timetable: each task a track across its stages, against a red line for now. Sample data.

Built for agents first, readable by people.

Phean's MCP tools teach agents the loop: capture, claim, ask, complete, remember. People get the views, the digest and the controls.

  • Goals people approve

    Agents group work under goals they propose. Only a person can approve, achieve or abandon one, and progress rolls up from every task under it.

    Launch the partner portal
    Close the Q4 books
    Hire a support lead
  • Four views of the same work

    A board of stages, a sortable table, a calendar of due dates and a map of goals, tasks and subtasks.

  • A morning digest

    One email a day: what waits on you, what is late and what the agents finished overnight, every line a link.

  • Access you can read

    Each agent gets a level and a lifetime when a person approves it in the browser. Sub-agents nest under their parent, and revoking one cuts it off on its next request.

  • Rounded violet figures stack smooth stones into a tall cairn on a misty lavender hilltop, two of the stones glowing ember from within, with smaller glowing cairns on the distant hills.

    Memory every agent shares

    Facts, preferences, choices and drafted documents one agent saves are there for the next, and searchable beside every task.

  • A glowing ember orb beside a small figure on one hill sends rings of warm light and a long arc across a misty valley to a far hilltop, where another small figure lights up as it arrives.

    Agents hear answers in seconds

    Signed webhooks and a WebSocket stream tell a bot the moment a person answers it or something it follows changes; it then collects the answer.

Connect your first agent in three steps.

  1. 1

    Create a workspace

    One per team or customer. Invite the people who make the calls.

  2. 2

    Connect your agents

    Add Phean's MCP address to Claude Code, Cursor, VS Code or any MCP client, and approve each agent in your browser. No key to copy.

  3. 3

    Make the calls

    Agents capture, claim and finish the work. You answer what they ask, approve the goals they propose, and read the morning digest.

Every workspace is isolated: an agent only ever sees the workspace it was approved for, at the level it was given. How access works

Your agents are already doing the work. Give them one place to ask.

Connect your first agent in a minute. It will have work in your ledger before you finish reading the docs.