OFFICIAL COPAW SITE

CoPaw is the Co Personal Agent Workstation for your AI assistant.

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.

Co Personal Agent WorkstationOpen-source personal AI assistantLocal, Docker, or cloud deployment

WHAT IS COPAW

CoPaw is built to be a real workstation for an AI assistant.

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

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.

PRODUCT CATEGORY

A personal AI workstation, not just a chat shell

CoPaw combines channels, browser console, Skills, memory, and workflow continuity into one product surface for individuals, teams, and operators.

OFFICIAL DOCS

The official CoPaw docs explain setup and operation

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 works like an operating desk for AI, not another prompt wrapper.

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

One assistant, wherever your team already talks

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

Deployment choices that match your constraints

Run locally, in Docker, or on managed infrastructure with the provider and model layer that fits your latency, privacy, and budget needs.

SKILLS

Extend behavior from the workspace itself

Skill instructions live beside scripts and docs, which keeps behavior legible and versionable instead of trapping it in hidden prompts.

HEARTBEAT

Keep useful work moving after the chat ends

Recurring digests, reminders, scheduled prompts, and maintenance jobs keep the system active between sessions.

MODEL MIX

Private by default, cloud when you choose

Pair local models with hosted providers and move between them without rebuilding the rest of the workflow surface.

CONSOLE

Operate the system through a readable control room

Inspect channel state, usage, tasks, Skills, and provider settings in a browser console designed for humans instead of only maintainers.

SYSTEM SHAPE

Product-first on the surface, AgentScope-backed underneath.

AgentScope gives CoPaw its technical footing, but the user-facing story is the workstation itself: runtime, console, documentation, and deployment paths that fit together.

Python runtime core

The runtime handles orchestration, providers, Skills, memory, token tracking, safety gates, and channel adapters.

Browser control room

A dedicated console keeps model switching, channel setup, visibility, and operations available to humans instead of hidden in scripts.

Docs as product surface

Setup guides, operating patterns, and reference pages are treated as part of the experience rather than an afterthought.

Practical deployment paths

You can start on a laptop, move to Docker, and later land in a hosted environment without rethinking the mental model.

CHANNEL FIT

Meet the assistant where attention already lives.

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.

Team chat

DingTalk, Feishu, QQ, Discord, Slack-style rooms, and group threads become working surfaces instead of notification noise.

Private conversation

Direct messages, personal reminders, and focused one-to-one threads stay lightweight while still carrying memory and Skills.

Operations surfaces

Console views, scheduled tasks, and CLI hooks give operators a place to steer the system beyond conversational UI.

DOCS

CoPaw Docs are part of the product, not a sidecar.

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.

FAQ

Questions people ask when they search for CoPaw and evaluate the product.

What does CoPaw stand for?

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.

Where are the official CoPaw docs?

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.

Is CoPaw meant for individuals, teams, or operators?

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.

Can it stay local-only?

Yes. Local models and local data paths are first-class. Hosted providers are optional, not assumed.

Why not just use a chat app with custom prompts?

Because prompts alone do not give you operating surfaces, recurring workflows, channel adapters, deployment paths, or workspace-native Skills.

Do I have to learn a big framework first?

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

Start with CoPaw, then expand only when the work asks for it.

Use the official CoPaw docs to stand up a first workstation, then iterate from your own channels, models, and operating rules.