Skip to main content

Agent Dock

The Bot dock is the web entrypoint for sending a selected bot into a selected space.

Main User Jobs​

  • Choose the bot and bot-bound space that match the workflow.
  • Attach files or source context when the work needs new artifacts.
  • Submit a focused space message without leaving the workspace route.
  • Review the queued operation and any artifacts or messages it creates.

Route And Context​

Primary route: /w/:workspace_ref. The exact controls visible on this surface depend on workspace permissions, selected artifact or bot, and feature configuration.

The dock lets users select a bot, choose a bot-bound space, attach files, inspect runtime status, and create durable web-originated operations. It shares the same bot runtime identity and artifact graph model as Telegram and MCP channels.

Key routes:

  • Bot list: GET /api/w/:workspace_ref/bots.
  • Space list: GET /api/w/:workspace_ref/spaces.
  • Runtime: GET /api/w/:workspace_ref/bots/:bot_ref/runtime.
  • Message: POST /api/w/:workspace_ref/spaces/:space_ref/messages.

Review Habits​

Use the app surface to get to the source context: open the relevant workspace, inspect the artifact or setting directly, and review any operation or event trail before treating derived output as final.

Planned media
  • Screenshot: Bot dock open with a selected bot, selected space, staged upload, and queued operation link. It helps users understand operation-backed space messages. Source: sample workspace with Bot dock enabled.