DreamLake

Agent apps

Available in CLI 0.108.0 and later.

This surface requires a server with Agent Apps enabled through the Connection v1 plane, provisioned indexes, and operator-configured provider OAuth clients. Source implementation and fixture tests do not establish production availability. Run dl apps list to check the target server; providers marked ready: false need operator setup.

App connections belong to your personal namespace. Connecting an account does not grant agent access. Grants apply to DreamLake's built-in agent, and each conversation turn also needs the Apps option enabled. Team and project membership do not inherit these accounts.

Connect and verify

Slack read consent covers accessible public/private conversations, direct messages, and files. Plaud exposes synced recordings, transcripts and existing summaries. Plaud remains read-only. Tokens stay on the server; the CLI opens the existing Connection OAuth browser flow.

bash
dl apps list --json
dl connection oauth create --connector slack-mcp --label "Work Slack" --access read
dl connection oauth create --connector plaud-mcp --label "My Plaud" --access read

Use the connection ID from the completed OAuth result or apps list. Pass --namespace <personal-slug> when your active namespace is an organization.

bash
dl apps grant <connection-id>
bash
dl apps check <connection-id> --json

check verifies authentication and supported tool discovery without reading account content; it does not grant access. tools requires an enabled grant and returns reviewed tools with current argument schemas. Unknown provider tools are excluded. Tool names and schemas can change: discover before constructing an input file.

bash
dl apps tools <connection-id> --json

Read and prepare

Write the discovered tool's arguments to a JSON object in a local file, maximum 16 KiB. Do not put OAuth tokens in that file.

bash
dl apps read <connection-id> <read-tool> --input-file query.json --json

Slack sending needs a separate provider authorization and an explicit grant. This still only lets the agent prepare proposals.

bash
dl connection oauth reconnect <connection-id> --connector slack-mcp --access read-write
dl apps grant <connection-id> --send
bash
dl apps prepare <connection-id> slack_send_message --input-file message.json --json

Preparing does not send a message. The response contains an action ID and a browser review path. Review the destination, thread, message, connection and account. Proposals expire after ten minutes; changes to credentials, grants, connection settings or the tool schema invalidate them.

bash
dl apps receipt <action-id> --json
bash
dl apps confirm <action-id>

confirm requires an interactive terminal, displays the exact payload, and defaults to declining. It has no --yes option and refuses --json. The server atomically claims the proposal: repeating confirmation cannot resend it. A lost provider response or failure to persist the outcome yields uncertain; inspect the receipt and Slack before creating a new proposal. Confirmation is never exposed as a model tool.

bash
dl apps cancel <action-id> --json
bash
dl apps revoke <connection-id>

Revocation stops future agent use, including returning reads whose grants changed while they were running. Already saved conversation content remains. Disable or delete the underlying account through dl connection when appropriate; revocation only removes agent access.

GUI and TypeScript API

Open Assistant connections at /<namespace>/builtin-agent/connections, or use /go My connections. In Apps for your agent, connect an account, allow reads and check the connection. Enable Apps in the agent composer. Prepared Slack messages appear in the same section for exact review and sending. The account Connections screen manages the account lifecycle.

The TypeScript API provides client.apps(namespace) with list, grant, check, tools, read, prepare, receipt, confirm and cancel. It uses explicit DreamLake credentials. The caller must obtain human authorization before confirm; do not register that method as an agent tool.

Results and receipts can contain private content. Store exported JSON accordingly. Provider error bodies and OAuth credentials are not part of these results.