Console
Operate CoPaw from the browser with provider, channel, and context controls.
Why the Console matters
Many agent projects stop at the runtime. CoPaw makes the browser Console part of the product because real users need a way to operate the system after installation.
The Console turns the runtime into a workstation:
- configure providers;
- test channels;
- inspect usage and chat state;
- switch models;
- manage context behavior;
- work with Skills and workspace settings.
What you should expect to do in the Console
Configure providers
The provider layer is where you decide whether the assistant talks to:
- hosted APIs;
- local models;
- OpenAI-compatible endpoints;
- hybrid setups that mix both.
Operate chat sessions
The Console is not just a settings page. It also acts as a place to run, inspect, and continue conversations in a productized interface.
Manage context and state
A long-lived assistant needs operational visibility. The Console is where CoPaw becomes easier to understand than a pile of scripts and environment variables.
Why this changes the website story
If the website only says "agent framework" or "AI assistant", it undersells the product. The Console proves that CoPaw is a usable operating surface, not only a backend capability.
Best practice
When presenting CoPaw on a homepage, show the Console as:
- a workstation control plane;
- the place where providers, channels, and context meet;
- evidence that the product is meant for repeat use, not only for one command-line session.