OpenTeam CLI Local Control

Overview

OpenTeam is controlled via the installed

openteamcli

command and local daemon. Do not directly click the browser interface, nor bypass the local control protocol to call the internal API of the Chrome extension.

Use this skill when a task requires multiple AI roles to discuss, review, critique, brainstorm, compare solutions, or provide independent perspectives in OpenTeam.

Local Command Requirements

By default, it directly calls

openteamcli

installed in the local PATH. If the command does not exist, prompt the user to install it from npm first:

bash

npm install -g @afumu/openteamcli

During development, you can execute in the OpenTeam repository:

bash

npm install -g ./packages/openteamcli

Or install using a soft link:

bash

npm link ./packages/openteamcli

Start and Check Connection First

Run the following before any operation:

bash

openteamcli daemon start
openteamcli doctor

daemon start

is an idempotent command. If the daemon is already running, it will only return

alreadyRunning

and will not restart the background process.

extension.connected

false

in the result:

Ask the user to open the OpenTeam plugin page.
Confirm that
```
Local Agent Control
```
is enabled in the settings.
Run
```
doctor
```
again.

If the daemon status is abnormal, prioritize running:

bash

openteamcli daemon restart
openteamcli doctor

Recommended New Task Flow

For new tasks, prioritize the process of "one-time creation of group chat, adding roles, publishing tasks, waiting for replies". This is most suitable for external Agent or CLI calls.

First create a JSON file, e.g.,

task.json

json

{
  "chat": {
    "name": "Solution Review",
    "mode": "independent"
  },
  "roles": [
    {
      "source": "temporary",
      "name": "Engineer",
      "systemPrompt": "Evaluate from the perspectives of engineering implementation, complexity, risk and testing."
    },
    {
      "source": "temporary",
      "name": "Product Manager",
      "systemPrompt": "Evaluate from the perspectives of user value, scope control and delivery rhythm."
    }
  ],
  "task": {
    "target": "all",
    "content": "Please evaluate this solution and provide risks, suggestions and final judgments."
  },
  "options": {
    "waitForReplies": true,
    "activateChat": true,
    "openTeamPage": true
  }
}

Then run:

bash

openteamcli run create-and-post --file task.json --wait

When reporting to the user, prioritize preserving perspective differences by role, do not flatten all replies into a single general summary.

Temporary Roles

If there is no ready-made template in the personnel library, do not require the user to manually create a template first. Directly use temporary roles in the task JSON:

json

{
  "source": "temporary",
  "name": "Researcher",
  "description": "Responsible for filling gaps and fact-checking.",
  "chatSite": "deepseek",
  "systemPrompt": "You are a researcher, responsible for verifying facts, identifying hypothesis loopholes, and listing information that needs to be supplemented."
}

Temporary roles belong only to the current group chat and will not be written into the personnel library. Available values for

chatSite

deepseek

chatgpt

gemini

claude

grok

If simulating the style of real public figures, company founders or experts, it must be clearly stated in the

systemPrompt

This is a simulated role of public ideological style.
It is not the real person themselves.
It does not speak on behalf of their company or organization.
It does not claim to have personal experience, real-time information or internal information.

Continue Existing Group Chat

When the user provides a

chatId

or wants to continue a previous OpenTeam group chat, use the existing group chat process:

bash

openteamcli task post --chat <chatId> --target all --content "Follow-up question"
openteamcli task wait --chat <chatId> --message <messageId> --timeout 300000
openteamcli task read --chat <chatId> --message <messageId>

If the CLI process of

task post

does not return for a long time, but

chat get

can already see user messages and role replies, it indicates that the group chat execution link may have been completed. At this point, use

task read

to read the result by message ID, and check if the daemon has pending requests:

bash

openteamcli daemon status

pending

is not

for a long time, restart the daemon to clear the pending status:

bash

openteamcli daemon restart

Common Commands

bash

openteamcli daemon start
openteamcli doctor
openteamcli daemon status
openteamcli daemon restart
openteamcli chat list
openteamcli chat get <chatId>
openteamcli chat create --name "Group Chat Name" --mode independent
openteamcli chat activate --chat <chatId>
openteamcli chat initialize --chat <chatId>
openteamcli role list --chat <chatId>
openteamcli role batch-add --chat <chatId> --file roles.json
openteamcli task post --chat <chatId> --target all --content "Task"
openteamcli task wait --chat <chatId> --message <messageId> --timeout 300000
openteamcli task read --chat <chatId> --message <messageId>

roles.json

can be an array:

json

[
  {
    "source": "temporary",
    "name": "Researcher",
    "systemPrompt": "Responsible for filling gaps and fact-checking."
  }
]

Error Recovery

Prioritize checking the machine-readable

error.code

Error Code	Handling Method
`extension_not_connected`	Ask the user to open the OpenTeam plugin page, confirm that Local Agent Control is enabled, then re-run `doctor` .
`control_disabled`	Ask the user to enable `Local Agent Control` in OpenTeam settings.
`role_not_ready`	Run `chat initialize --chat <chatId>` , or ask the user to wait for the role iframe initialization to complete.
`task_timeout`	Run `task read` and report the received partial replies and roles still waiting.
`permission_denied`	Do not retry blindly. The local token or daemon status may be abnormal; first run `daemon restart` .
`fetch failed`	First run `doctor` and `daemon status` . If the daemon exits or the plugin is disconnected, restart the daemon and reopen the OpenTeam page.

Operation Rules

Prioritize using
```
run create-and-post --file ... --wait
```
for new tasks.
Multi-role, long prompt or complex tasks must use JSON files to carry input.
Do not write keys, tokens, cookies or user privacy information into task prompts.
The local daemon can only listen to
```
127.0.0.1
```
; do not expose it to the public network or local area network.
Do not publish tasks to OpenTeam on behalf of the user unless the user explicitly wants the AI roles in the browser session to act.
When reporting results, specify which roles have replied, which roles are still waiting, and whether there was a timeout.

openteam-control

NPX Install

Tags

SKILL.md Content (Chinese)

OpenTeam CLI Local Control

Overview

Local Command Requirements

Start and Check Connection First

Recommended New Task Flow

Temporary Roles

Continue Existing Group Chat

Common Commands

Error Recovery

Operation Rules