agentscope-ai / agentscope-ai/QwenPaw

[Feature Request] Support Headless Mode and Standardized RPC/WebSocket API for Third-Party UI Integration

Open
#1,185 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
34.9k
Forks
3.1k
Avg merge
1d 15h
Merged PRs (30d)
225

Description

![Image](https://github.com/user-attachments/assets/ec47bfae-4a6d-4081-8e1b-8699e0d2a0d7)

Is your feature request related to a problem?
Currently, CoPAW provides a highly integrated desktop environment for Agent management. However, for developers who have already built their own specialized productivity tools (like my project OmniTool, which handles daily workflows, system-level screen capture, and specific UI layouts), it is difficult to leverage CoPAW's powerful Agent orchestration and memory management without running the full CoPAW GUI.

Running two heavy Electron/Desktop UIs simultaneously is resource-intensive and creates a fragmented user experience.

Describe the solution you'd like
I propose implementing a "Headless Mode" for the CoPAW engine, allowing it to run as a background service. This service should expose a standardized API (preferably via WebSocket for real-time Agent communication or gRPC/REST for stateless tasks).

Key Requirements:

Engine/UI Decoupling: Ability to launch the CoPAW core (AgentScope backend + Memory/Vector DB) without the main window.

Standardized Protocol: A clear API schema to:

Trigger specific Agents.

Stream chat responses (SSE or WebSocket).

Query/Update the long-term memory (RAG) storage.

Manage the "Sandbox" environment remotely.

Authentication: A simple Token-based mechanism for local inter-process communication (IPC) security.

Describe alternatives you've considered
Running CoPAW in the background: This still consumes significant GPU/RAM for the UI rendering process.

Directly integrating AgentScope SDK: This loses the "State" and "Memory" persistence that the CoPAW desktop app manages so well.

Additional context
I am developing OmniTool, a personal workspace focused on native OS integration (screenshot, screen recording, system-level diary). By having a Headless CoPAW, I could:

Use OmniTool as the "Sensing & Interaction Layer" (The Eyes and Hands).

Use CoPAW as the "Cognitive & Memory Layer" (The Brain).

This separation would allow CoPAW to become the de-facto backend for various third-party AI desktop applications.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.