Docs · Desktop
OPC teams
An OPC team is the AI team of a one-person company: agents on your phones and your computer working together, with Lom as the leader. You give the leader the goal. It first maps the team to learn what each member can do, then assigns, checks and reports. Keep each team focused on one goal.
Create a team
- On the left, open OPC teams OPC团队 → New team 新建团队.
- Add members from All assistants 所有助手: paired phones, or desktop agents found under Settings → Agents (the list notes what each is good at). Lom becomes the leader automatically.
- Give each member a role, such as "orders food", "watches videos" or "writes code". The same assistant can be added more than once for different roles.
- Name the team and choose a work folder (the leader keeps its team memory,
TEAM.md, there), then click Create 确认创建.
Only Lom can leadOnly Lom can direct phones and other agents. Desktop agents on the team use their own models and quotas.
The leader maps the team first
Whenever it gets an order, the leader starts by mapping the team. It reads TEAM.md in the team folder; if the file doesn't exist, is more than 24 hours old, or the members have changed, it surveys everyone again:
- Phone members: online or not, battery and network, which apps are installed, whether accessibility is on. For apps that matter to this job (Meituan, Taobao, Douyin, Xiaohongshu, WeChat…), it has the phone open them to see whether they're signed in. It only looks; it doesn't act. A phone signed in to Meituan, for example, can order food and run errands.
- Desktop agents: not tested; their strengths are noted from the table below.
The map goes into TEAM.md: what each member can and can't do, which apps are signed in, battery, permissions and when it was updated. It is the team's memory, and you can open and edit it yourself.
# Food delivery squad · updated 10-16 11:20
## Phone 1 (REDMI)
- Online · battery 82% · Wi-Fi · accessibility on
- Signed in: Meituan, Xiaohongshu, WeChat → can order food, run errands, post notes
- Not signed in: Taobao
## Codex CLI
- Strong; good at controlling the computer, coding and editing files
## Kimi
- Good at watching videos and reading long documents and web pagesPhones need a recent versionListing installed apps needs Lom Agent from 2026-10-16 or later. With an older phone, the leader only sees online status and battery.
What desktop agents are good at
| Agent | Strength the leader notes |
|---|---|
| Codex CLI | Strong; good at controlling the computer (computer use), coding and editing files |
| Claude Code | Coding, long tasks and writing |
| Kimi | Watching videos and reading long documents and web pages |
| Pi | Coding |
| CodeBuddy | Inexpensive; good for batch work |
| Gemini CLI | Reading images, watching videos and research |
| Qwen | Chinese writing and coding |
| Others | General coding agent |
Assign, check, report
- Assign: split the job by the map. Phone work goes to the right phone; computer work goes to the right agent.
- Check: after assigning, read back each member's real result. "Received" doesn't mean done; unfinished work gets a follow-up or goes to someone else.
- Report: gather everyone's results into a summary for you.
Outside actions ask you firstPaying, ordering, publishing and private messages always come to you first, and happen only after you agree.
Members message each other directly
Desktop agent members can talk to each other without going through the leader. For example, tell Codex CLI in its pane "write a prompt and send it to Kimi"; Codex writes it and sends it straight to Kimi's pane, and Kimi starts on it.
- Incoming messages show in the member's pane as a "Message from …" card.
- Members act on messages as needed and don't have to reply to each one; they reply when the sender needs the result.
- The leader uses the same channel to give desktop agents work and extra instructions, and they notify the leader when they finish.
- Phone members are still directed by the leader: it assigns them tasks and reads back the real results.
Team group chat
Besides one pane per member, the team page has a “group chat” view (desktop 0.3.8 and later): you, the leader, every member and your personal assistant on one timeline.
- @ someone, they receive it: pick members in the input box (or @everyone) and the message goes only to the independent sessions of those members, once each. For now you can @ the leader and desktop agents; phone members cannot be @-mentioned in the group chat yet (see “Phone members” below). With no @, it goes to the leader by default and is never broadcast to everyone. A line above the input always says who it is sent to.
- Assignments and reports are visible: what the leader gave to whom, and each member's report to the leader when their round ends, appear on the timeline and say which task they belong to.
- Your assistant is in it too: work the assistant sends to the team, and the reminder that returns to the assistant's session when it is done, are shown as well.
- Open any member for details: every member entry opens that member's own session with the full run record. The group chat is built from the real sessions with no separate copy, so switching views, reconnecting or reopening the team never sends or runs anything twice.
- Status shows facts: typing, running, waiting for confirmation, done and failed all come from what really happened in the session. When the connection drops it shows “status to be verified” instead of spinning forever.
- Phone members coming soon: for now the leader can assign work to a phone (the official phone app or Mika) and the result returns to the leader through the phone's receipt; to message a phone on its own, use its pane in the side-by-side view. @-mentioning a phone member directly in the group chat and showing phone progress there are still in development. With @everyone, a phone shows “not delivered”.
- Stop any time: the “Stop team” control still works.
The collaboration chain
This is what a “workflow” looks like in Lom. There is no flow chart to drag around; it is a chain that happens naturally in the group chat:
- You @ the leader in the group chat and state the goal.
- The leader assigns work by the capability map, to desktop agents, and can also assign it to phones (the official phone app or Mika).
- Desktop agents finish and report the real result to the leader in the group chat; a phone's result returns to the leader through the phone's receipt (showing phones in the group chat is coming soon).
- The leader checks the results and summarizes them for you. For outward actions like payments, publishing or direct messages, it always asks you first.
Dispatch counts and known limitsA personal assistant can only dispatch a limited number of times along one chain; at the limit it stops dispatching automatically and waits for your new instruction, and the group chat shows which dispatch in the chain it is. The internal leader-and-member collaboration loop is scheduled by the core, so the desktop can show it but not intercept it, and it does not yet have the same automatic limit; use “Stop team” when needed.
A pane for every member
- The team page has a pane for each member showing its real conversation and progress. You can focus on one member (enlarge it) or open the full record in a task 在任务里打开.
- State goals in the leader's pane; a message in a member's pane gives that member work directly.
- A desktop agent's pane shows its own model at the bottom right, and you can switch it.
- Stop team 停止团队 stops every member's current turn, including phone tasks the leader started that are still running.
Tips
- Keep one team on one goal, such as a "Xiaohongshu content studio" or a "food delivery squad"; the leader's map gets more accurate.
- When a team includes a demo phone, you only see demo records; use a real phone to actually run tasks.
- Phone members must be online with accessibility on; see Phone setup.