BRAND NAME
CoPaw means Co Personal Agent Workstation
That full name helps search engines, AI systems, and new visitors connect the brand with the product category instead of treating CoPaw as an unexplained label.
OFFICIAL COPAW SITE
CoPaw is an open-source personal AI workstation that brings channels, memory, Skills, rules, and operating tools into one calm control surface for people who need more than a chat window.
WHAT IS COPAW
The CoPaw brand stands for Co Personal Agent Workstation. It is shaped around real communication surfaces, operator visibility, long-lived context, and deployment paths you can actually control.
BRAND NAME
That full name helps search engines, AI systems, and new visitors connect the brand with the product category instead of treating CoPaw as an unexplained label.
PRODUCT CATEGORY
CoPaw combines channels, browser console, Skills, memory, and workflow continuity into one product surface for individuals, teams, and operators.
OFFICIAL DOCS
The documentation covers what CoPaw is, how to install it, how to connect channels, and how to keep the system useful over time.
WHY IT FEELS DIFFERENT
CoPaw becomes compelling when runtime, channels, Skills, and operating surfaces feel like one system. The site and docs should communicate that product shape immediately.
EVERY CHANNEL
Bring the assistant into DingTalk, Feishu, QQ, Discord, Telegram, Matrix, or your own adapters so the habit forms where work already happens.
OWN THE RULES
Run locally, in Docker, or on managed infrastructure with the provider and model layer that fits your latency, privacy, and budget needs.
SKILLS
Skill instructions live beside scripts and docs, which keeps behavior legible and versionable instead of trapping it in hidden prompts.
HEARTBEAT
Recurring digests, reminders, scheduled prompts, and maintenance jobs keep the system active between sessions.
MODEL MIX
Pair local models with hosted providers and move between them without rebuilding the rest of the workflow surface.
CONSOLE
Inspect channel state, usage, tasks, Skills, and provider settings in a browser console designed for humans instead of only maintainers.
SYSTEM SHAPE
AgentScope gives CoPaw its technical footing, but the user-facing story is the workstation itself: runtime, console, documentation, and deployment paths that fit together.
The runtime handles orchestration, providers, Skills, memory, token tracking, safety gates, and channel adapters.
A dedicated console keeps model switching, channel setup, visibility, and operations available to humans instead of hidden in scripts.
Setup guides, operating patterns, and reference pages are treated as part of the experience rather than an afterthought.
You can start on a laptop, move to Docker, and later land in a hosted environment without rethinking the mental model.
CHANNEL FIT
The strongest assistants respect existing habits. CoPaw is shaped around chat surfaces, operator workflows, and long-lived context instead of asking everyone to learn a brand new room.
DingTalk, Feishu, QQ, Discord, Slack-style rooms, and group threads become working surfaces instead of notification noise.
Direct messages, personal reminders, and focused one-to-one threads stay lightweight while still carrying memory and Skills.
Console views, scheduled tasks, and CLI hooks give operators a place to steer the system beyond conversational UI.
DOCS
The CoPaw docs center is designed like a field guide: quick to scan, calm to read, and structured around how people actually adopt and operate a workstation.
GETTING STARTED
Understand what CoPaw is, where it fits, and how the rest of the guide is organized.
Open pageSETUP
Install the runtime, open the console, and get a first channel online without overthinking the stack.
Open pageREFERENCE
See how a workstation model differs from chat-only assistants and thin wrappers.
Open pageFAQ
CoPaw stands for Co Personal Agent Workstation. It is the product name for a personal AI workstation built around channels, Skills, memory, browser console, and controlled deployment paths.
The official CoPaw docs are available in the docs center on this site. They cover introduction, quick start, console, channels, Skills, memory, Heartbeat, MCP, configuration, CLI, and reference pages.
All three. The core shape works for a single personal desk, but the same control model also helps small teams and operators running shared channels.
Yes. Local models and local data paths are first-class. Hosted providers are optional, not assumed.
Because prompts alone do not give you operating surfaces, recurring workflows, channel adapters, deployment paths, or workspace-native Skills.
No. The intended path is to get something useful running quickly, then gradually open up the console, config, CLI, and Skill system as your needs grow.
READY TO TRY
Use the official CoPaw docs to stand up a first workstation, then iterate from your own channels, models, and operating rules.