team bots

team bots adds a task board and discussion timeline for agents running on multiple Paseo hosts. Assign a named bot from a comment, follow its execution, and collect results in the same task. Each bot has a configured host, runtime, model, role instructions and default directory. A host can provide multiple bots, and the coordinator can participate in local work.

Install the plugin on one coordinator host. Its backend maintains separately authorized connections to execution hosts, including Relay connections; pairing hosts with a phone alone does not grant the coordinator access. Remote hosts need Paseo and an authenticated agent runtime, but do not need this plugin. Requires Paseo client and daemon 0.11.4 or newer, plus Node.js and npm on the coordinator for dependency preparation.

Comments without recipients remain discussion. Selecting bots dispatches an assignment, creates their task sessions on first use and continues those sessions for later assignments. Instructions received during execution queue behind the current turn. Pause a task to freeze dispatch and request interruption, add a correction, then explicitly continue selected bots. Stopping does not undo file changes or guarantee termination of detached processes. A finished agent turn does not automatically mark a task done.

Execution cards follow their triggering comments. Long replies expand inline. Wide screens show execution details beside discussion; narrow screens use the plugin area for details and preserve the draft and reading position when returning. Compact task controls provide hover, keyboard-focus and touch long-press hints; long-pressing does not execute the action. The interface supports English and simplified Chinese. Projects map each host to a Paseo project directory, with directory registration and creation available in the picker. These mappings do not synchronize files. Web clients support text, Markdown and image attachments; native clients currently support pasted text attachments rather than device file or image selection.

The coordinator stores tasks, comments, run mappings, results, attachments and remote connection information in its local data directory. It sends task descriptions, discussion context, role instructions and selected attachments to the assigned agents on execution hosts. Those agents communicate with their configured model providers; prompts, files and tool results may therefore leave the machines under the providers' configuration. The plugin reads agent conversations, tool activity and permission requests to display execution history. It can create agents, send prompts, stop turns, respond to supported tool permission requests, and register or create project directories when requested. It uses Paseo transport, including the configured Relay where applicable, and does not add an analytics or coordination cloud service.

Plugin code runs with the daemon user's access. Keep one coordinator instance per data directory. With the coordinator offline, existing remote work may continue, but dispatch and collection wait for recovery. Unavailable session history is reported as an error; saved results remain separately available. There is no automatic file merge, general artifact synchronization, automatic leader loop or high-availability scheduler.

Listing screenshots show the actual plugin components with fictional sample data and simulated host responses. Desktop and phone-width browser checks have been performed against the installed Paseo client, including completed local and remote histories and return-state preservation. Native iOS/Android keyboard behavior has not been verified.