@easbot/agent 0.2.15 → 0.2.18

package/dist/assets/txt/tool/agent-client-chat.txt

@@ -1,52 +1,72 @@
 Manage a full-duplex conversation channel with another easbot agent endpoint.
-Use this as the single tool for connect, list, capabilities, send, status, config, interrupt, and close.
+Use this as the single tool for connect, list, discover, capabilities, send, status, config, interrupt, and close.
 
 Inputs (kept minimal):
-- operation: connect | list | capabilities | send | status | config | interrupt | close
-- baseUrl: target easbot service base URL (required by connect)
-- connectionId: local managed connection id (required after connect)
-- prompt: message to send (required by send)
+- operation: connect | list | discover | capabilities | send | status | config | interrupt | close
+- baseUrl: target easbot service base URL (required for connect, e.g. http://localhost:3000)
+- connectionId: local connection id (required for remote ops: capabilities/send/interrupt/close/status; auto-resolved from baseUrl if not provided)
+- prompt: message to send (required for send)
 
-Behavior:
-- Local operations (no remote RPC):
-  - config: inspect local agent config and managed connections
-  - list: list local managed connections
-  - status: inspect local managed connection state
-  - close: release local connection state and cleanup interaction resources
-- Remote operations (requires target agent service):
-  - connect: create/reuse remote session and bind to local connectionId
-  - capabilities: query remote agent capabilities (ACP initialize)
-  - send: push one message to remote session (async; no waiting)
-    - before sending, you must have an active connectionId (connect first). The tool will automatically ensure an event subscription and stream remote responses back into the local SessionPrompt (no extra action from the LLM is required).
-  - interrupt: cancel the remote session and cleanup local interaction state
-    - use this when you need to abort an ongoing interaction
-    - sends an interrupt signal to the remote server which will cancel the session
-- Local mapping persists in .easbot/client-connections.json
-- All message receiving is done via event streaming (WebSocket/SSE/STDIO)
+Operations:
+1. connect: Create or reuse a remote session, bind to local connectionId
+   - Required: baseUrl (connectionId not needed)
+   - Returns: connectionId, sessionId, remoteAgentId, channel
+   - No service registration required; pure URL connection is supported
+2. list: List all locally managed connections (active sessions)
+   - Returns: array of connection info with connectionId, baseUrl, sessionId, remoteAgentId
+3. discover: Discover available agent services from registry
+   - Data sources: local config file (.easbot/agent-services.json), Config.Info.acp.clients, Gateway
+   - Returns: array of AgentServiceInfo { id, name, baseUrl, agentId, capabilities, status, metadata }
+4. capabilities: Query remote agent capabilities (ACP initialize)
+   - Required: connectionId (auto-resolved from baseUrl)
+   - Returns: protocolVersion, agentCapabilities, authMethods
+5. send: Push one message to remote session
+   - Required: connectionId, prompt
+   - Automatically establishes event subscription on first send
+   - Remote responses are injected into local SessionPrompt asynchronously
+   - Returns: pending round info (waiting for remote response)
+6. status: Inspect local managed connection state
+   - Required: connectionId (auto-resolved from baseUrl)
+   - Returns: connection state including sessionId, baseUrl, remoteAgentId, channel
+7. config: Inspect local agent client config and managed connections count
+   - Returns: acp config object and managedConnections count
+8. interrupt: Cancel remote session and cleanup local interaction state
+   - Required: connectionId (auto-resolved from baseUrl)
+   - Sends interrupt signal to remote server, cancels subscription
+   - Use when you need to abort an ongoing interaction
+9. close: Release local connection state and cleanup all interaction resources
+   - Required: connectionId (auto-resolved from baseUrl)
+   - Always call close when done to prevent resource leaks
+
+Connection Flow:
+1. connect + baseUrl → creates connection, returns connectionId
+2. Other operations use connectionId → auto-resolved from baseUrl if not provided
+3. If baseUrl provided but no connectionId, searches existing connections by baseUrl
+4. If no matching connection found, connect operation is required first
+5. Use discover to find available services before connecting
+
+Local vs Remote Operations:
+- Local (no remote RPC): config, list, discover
+- Remote (requires connectionId after connect): capabilities, send, status, interrupt, close
 
 Round Control:
 - Each connection has a maximum of 10 interaction rounds by default
 - One round = one question (send) + one answer (received response)
-- When round limit is reached, the subscription is automatically cancelled
-- Use `close` operation to manually cleanup when interaction is complete
-
-Interrupt Signal:
-- The tool automatically listens for abort signals from the local agent
-- When the local agent is interrupted (e.g., user cancels), the tool will:
-  1. Send an interrupt signal to the remote server
-  2. Cancel the local subscription
-  3. Cleanup the interaction state
-- You can also manually trigger interrupt using the `interrupt` operation
+- When round limit is reached, subscription is automatically cancelled
+- Use `close` to manually cleanup when interaction is complete
 
 Returns:
-- connectionId and remote sessionId
-- capabilities: protocolVersion, agentCapabilities, authMethods
-- subscription readiness for event-based message receiving
-  - the tool does not expose a subscribe operation; it establishes subscription automatically on first send to forward remote responses into the local conversation
+- Standard tool result: { title, metadata: { count, ... }, output: JSON }
+- connectionId: local connection identifier
+- remote sessionId: remote session identifier
+- subscription: automatically established on first send
 - round info: completedRounds, pendingRound, maxRounds, remaining rounds
 
 Notes:
-- Sending without a prior connect (no usable connectionId) will fail with an explicit error instructing the agent to connect first.
-- The tool appends a minimal async hint to the prompt to clarify non-blocking behavior.
-- IMPORTANT: Always call `close` when you are done with the interaction to cleanup resources (subscription, connection state). This prevents resource leaks.
-- Use `interrupt` if you need to abort an ongoing interaction before completion.
+- Send without prior connect will fail with explicit error
+- The tool automatically establishes subscription on first send
+- Remote responses flow back via subscription into local conversation
+- IMPORTANT: Always call `close` when interaction is complete to cleanup resources
+- Use `interrupt` to abort an ongoing interaction before completion
+- Pure URL connection: no service registration needed, just provide baseUrl
+- Use discover to find available agent services before connecting