Channels
Placet Channel
Facio's primary operator channel for approvals, management, onboarding, and streaming.
Placet is the default operator surface because it can represent the runtime state better than a plain chat channel: streamed progress, structured forms, approvals, file-heavy review, management controls, and multi-agent registration.
Config fields
| Field | Meaning |
|---|---|
enabled | Start the Placet channel. Quickstart enables it when FACIO_PLACET_INSTANCE_URL is present. |
instanceUrl | Placet base URL. Bundled quickstart defaults to http://placet:8080. |
apiKey | Placet API key. Quickstart maps it from PLACET_API_KEY to FACIO_PLACET_API_KEY. |
agentId | Optional stable Placet agent ID. Empty lets Facio auto-create or register. |
agentName | Visible name in Placet. |
channelTag | Optional tag for grouping. |
streaming | Enable streaming output. |
allowFrom | Default is ['*'] because Placet handles workspace access upstream. |
autoCreateAgent | Let Facio create/register the agent in Placet. |
managementPublicUrl | URL Placet should call for Facio management API. |
managementToken | Bearer token Placet uses for /api/v1/*. Usually mirrors FACIO_MANAGEMENT_TOKEN. |
Quickstart mapping
.env | Facio variable |
|---|---|
PLACET_API_KEY | FACIO_PLACET_API_KEY |
FACIO_PLACET_INSTANCE_URL | Placet URL for bundled or external mode. |
FACIO_AGENT_NAME | Visible agent name. |
FACIO_MANAGEMENT_TOKEN | Secures Facio management API and is announced to Placet. |
FACIO_MANAGEMENT_URL | Management callback URL for this agent. |
What Placet gets from Facio
- Agent registration and visible agent metadata.
- Slash command metadata for channel menus.
- Management URL and bearer token for settings, credentials, MCP, sessions, audit, and operations.
- Streaming message updates and final status.
- Provider onboarding forms when no usable provider is configured.
- Structured review and credential forms where supported.
Provider onboarding
If Facio starts without a working provider, the runtime can still start and Placet can show setup forms. The operator can select a provider, provide API key/base URL where required, validate the provider, and persist it without editing files manually.