01
OpenAI-compatible gateway
Point compatible SDKs at PasClaw for chat completions, responses, and model discovery while retaining PasClaw's tools and provider routing.
// Run it as a service
One binary, every surface
The same executable can serve applications, browser users, and chat channels without splitting the agent into multiple deployments.
OpenAI APIEmbedded web UI9 chat channelsSingle deploy
02
Embedded control panel
The built-in web interface provides chat, memory, file, MCP, schedule, skill, log, and settings workflows from the running binary.
03
Meet users where they are
Connect Telegram, Discord, Slack, LINE, WhatsApp, Matrix, IRC, email, and Teams with sender identity and allowlist controls.
04
One operational unit
Updates, logs, configuration, and policy remain centered on one process instead of a fleet of adapters and frontend services.
From the documentation
Technical details
Implementation notes drawn from the PasClaw repository documentation.
Gateway surfaces
gateway starts the full web control surface, while serve provides the API-oriented runtime. The default listener is loopback on port 8088.
- OpenAI-compatible chat completions and Responses endpoints are included.
- Health, version, stats, logs, filesystem, memory, cron, skills, MCP, and config routes support operations.
- Bearer authentication can be supplied through PASCLAW_GATEWAY_TOKEN.
Embedded and connected
TPasClawServer can host the service in an existing process, and channels connect the same agent to messaging systems.
- Telegram, LINE, WhatsApp, Matrix, IRC, and email support bidirectional flows.
- Discord, Slack, Teams, and generic webhooks are documented as outbound surfaces.
- Sender identity and allowlists remain part of channel policy.
Source documentation
Common questions
Frequently asked questions
Keep exploring
See how the rest of PasClaw fits together.