Meet Pytheus
Pytheus is your AI cofounder on every plan. It reads your company, plan and Library, answers, researches, runs code on its own computer and briefs your team.
Updated 2026-10-13
Pytheus is the one agent you always have. It leads the team, has its own cloud computer, and knows your company from the moment onboarding finishes. You talk to it in HQ, from the Ask screen.
What Pytheus knows
- Your company dossier: product, customers, problem, goal, traction and competitors.
- Your plan: the stage, the tasks, their status and what is blocked.
- The team’s shared memory, and what the team finished recently.
- Your Library, your other chats (it can search them) and the files you attach.
Three ways of working
Before Pytheus answers, Pythe decides how much machinery your message needs. The lightest mode that can do the job wins. This is decided by rules alone, so no model call stands between you and the first words. A message the rules cannot place is given every tool and the model decides; a plan card appears only if the computer actually opens.
| Mode | What it is for | Tools | Model turns |
|---|---|---|---|
| Chat | Greetings, opinions, advice from what it already knows, “how is it going”. | None | 2 |
| Think | Looking things up without a computer: web research, team memory, delegating. | Research, memory, the plan, the team. No computer, files or browser. | 12 |
| Computer | Real work on its cloud computer: run code, build or read files, open specific web pages. | Everything, including its computer. | 14 |
When the computer opens, a short line tells you why. You can override this for a message with the + menu in the composer: Computer: Auto (the default, opens it when the job needs it), Off (never) or On (always). See Chats and the composer.
What Pytheus can do
| Capability | Tools |
|---|---|
| Work on its computer | sandbox_exec, write_file, read_file, list_files, browse_page |
| Research and save | web_research, save_to_library, find_in_chats |
| Make files and sites | create_document, edit_office_file, read_document, analyze_data, website_create, website_edit, screenshot_page, deploy_website (always asks first) |
| Read and change your plan | show_roadmap_tasks, add_roadmap_task, update_roadmap_task |
| Remember | remember, recall. See Shared memory. |
| Lead the team | list_team, delegate_to_employee, propose_hire, create_group_chat, open_chat |
| Track work | assign_task, check_work, log_progress, list_tasks. See Tracked tasks. |
| Ask for an app | request_connector, which puts a Connect button in the chat. |
| Plan its own work | plan |
| Extend the team | create_tool, list_tools, and any custom tool_* the team has made. See Tools. |
One live run per chat
Pytheus’s answer is a durable run, so closing the tab does not lose it. Each chat has at most one live Pytheus run. What you send while it works depends on its state.
| Pytheus is… | Your message… |
|---|---|
| Working | Goes into its inbox and steers it. It reads it before its next step. |
| Waiting for your answer to a question | Answers the question and resumes the run. |
| Waiting for an approval | Gets a quick reply saying what it is waiting on. Your message is kept for when it carries on. |
| Idle | Starts a new run. |
Honest answers
The server decides what was delivered from what the tools actually returned, not from the model’s words. If a file was not saved, the answer says so first. See Reports and delivery.