Integrations
TUI and web share an Integrations section at the end of the sidebar. Select a connection with ↑/↓ and Enter, or click it. Esc returns to the integration list.
Decisions contains Decisions API: provider configuration, delegated-task
model routing, project/provider budgets and measured cost/savings. Existing
#/decisions-api, #/jev and #/ai-review links still open this panel. Its current
link is #/integrations?item=decisions.
Web access contains Web links, at #/integrations?item=web-access.
Choose automatic routing, Cloudflare Tunnel, localhost.run, ngrok, or your own
HTTPS domain. Settings and encrypted tunnel credentials belong to the controller
and apply at the next web start. Settings → Web Access → p opens this same integration;
it does not restart sessions. The public tunnel runs alongside the server web
gateway when the controller is remote. Its server-local address is localhost on
that server, not on your laptop. Temporary tunnel addresses can change after a
reconnect; use the current link from ./devctl web status or a stable domain.
Remote interface contains Telegram, Slack (source access required) and Microsoft Teams (source access required). These are independent optional messenger packages, not alternative session implementations. The three use the same controller user scope, existing terminal input ownership and MCP approval delivery. They support:
- Project/session navigation and a bounded plain-text terminal view.
- Reply to a selected existing session, with a separate Enter submission.
- Session attention notifications and MCP request/delivery notifications.
- Individual Allow/Limit selection, approval and denial using the same lifecycle as the normal console.
External MCP clients contains Private MCP, at
#/integrations?item=private-mcp. The optional OpenAI Secure MCP Tunnel package
lets ChatGPT call the server operator API through outbound HTTPS. Configure its
tunnel ID and encrypted restricted runtime key, then explicitly start operator
access. The connection runs on the controller server without your laptop.
This requires the recovery operator and grants full server management authority
to authorized users of that upstream tunnel; it is separate from Project MCP.
Setup, health, cleanup and Claude/Antigravity alternatives.
Messenger access does not launch arbitrary shells, widen project permissions, restart sessions, transfer account credentials into a bot or override another terminal's input owner. Detach the current terminal owner before replying in chat. Prompt delivery is at most once; after an uncertain network failure, inspect the session before resending.
Configure a remote interface
Install the optional provider package in the controller, using the existing package loader. Bundled checkouts include Telegram, Slack and Teams as optional controller dependencies. Without installed packages or credentials, TUI/web and all existing sessions continue working normally.
A console administrator selects Add/replace credentials. Inputs stay hidden and are stored in the encrypted controller keyring. Slack requires a bot token and app-level Socket Mode token. Teams requires its tenant ID, bot application ID and client secret. Telegram keeps its existing bot-token setup.
Each signed-in console user selects Pair my chat and enters their own upstream user ID. Telegram returns an expiring link; Slack returns a code and HTTPS app link; Teams returns a code to send in its installed bot's personal chat. Pairing checks the exact upstream user identity, private conversation and configured workspace or tenant. Codes expire after five minutes and are stored as hashes. Disabled console users cannot operate or receive notifications.
Telegram and Slack use outbound connections. Teams also requires a stable public HTTPS Azure Bot messaging endpoint:
https://YOUR-CONSOLE/v1/messengers/teams/events
This exact POST route preserves the Bot Connector JWT through the web gateway. The Teams package validates its signature, issuer, audience, expiry, signed service URL and Teams channel endorsement before processing a message. Other messenger routes remain behind normal console authorization. Public Azure, single-tenant applications and personal chats are supported; sovereign clouds, anonymous/emulator messages and group conversations are not enabled.
Controller API
| Method | Path | Purpose |
|---|---|---|
| GET | /v1/messengers |
Installed packages, setup field names and this user's connection status |
| PUT | /v1/messengers/:id |
Administrator-only enable/disable and encrypted credential replacement/removal |
| POST | /v1/messengers/:id/pair |
Current user's one-time pairing, {externalUserId} |
| DELETE | /v1/messengers/:id/binding |
Disconnect only the current user |
| POST | /v1/messengers/:id/events |
Optional upstream-authenticated event delivery |
Multi-field replacement uses {enabled:true, credentials:{...}}. Values never
appear in status, snapshots or provider state. Telegram's existing {token} form
remains compatible. {enabled:false, removeToken:true} explicitly removes the
stored credential. Per-provider configuration updates run sequentially, avoiding
overlapping connections when two settings requests arrive together.
Verification
Normal package and controller tests mock external APIs and send no real messages.
Opt-in Docker tests use isolated mock infrastructure and remove only their own
test containers. Slack (source access required) documents its pinned Socket Mode mock;
Teams (source access required) documents its HTTP/JWKS/OAuth mock with full production JWT
validation. Telegram's Docker test uses watzon/tg-mock:
docker run --rm --name devctl-telegram-mock -p 127.0.0.1:8081:8081 \
ghcr.io/watzon/tg-mock:latest --faker-seed 12345
DEVCTL_TELEGRAM_MOCK_URL=http://127.0.0.1:8081 \
node --test packages/provider-telegram/docker.integration.test.mjs
Only the injected test transport maps official upstream hosts to loopback. A production configuration cannot select an arbitrary API host or disable request authentication.