Disconnecting removes the channel row, deletes the matching secret from the keychain, and forgets any remembered sign-in tokens. Already-synced messages are explicitly kept — they only lose their reference to the deleted channel. A foreign tool server, by contrast, needs approval for EVERY single call until the user has approved that specific tool once.

Contents

Docs overview

Connections · Disconnecting & tool servers

Disconnected means genuinely gone

Disconnecting a connection is more than turning a green dot grey. This page describes what actually gets deleted — and what explicitly stays — and how a foreign tool server differs from an ordinary connection.

What happens when you disconnect

The channel row: Is deleted — this is the click that triggers everything else.
The keychain secret: Is deleted in its own right, not just orphaned — the password or token is no longer retrievable anywhere afterwards.
Cached sign-in tokens: Microsoft and Google tokens are explicitly forgotten, so no silent re-authentication is left behind.
Already-synced messages: Are explicitly kept — there is no delete cascade for them, only their reference to the deleted channel is cleared.
Anything already learned: Contacts and memory entries that arose via that channel remain in place too, and must be deleted separately.

Three tiles from the “Connections” window re-enacted Re-enacted excerpt from the “Connections” window: a mailbox and a calendar show as connected, a Nextcloud file store shows as disrupted — each tile with its type and display name.

Foreign tool servers (MCP)

A foreign tool server is registered by command or address, with an optional credential — that credential moves into the keychain and never comes back out; the interface only sees THAT one exists. Unlike an ordinary connection, a not-yet-approved foreign tool carries the highest approval class: every single call presents a card, regardless of the autonomy level and regardless of any “without approval” switch — until the user has explicitly approved that one specific tool.

Known gaps in this documentation build (as of 26 Sept 2026)

A fixed upper limit on the number of simultaneous accounts per type could not be found in the source — several accounts per type are supported in multiple places, but behave inconsistently by channel type (mailboxes throughout, other types sometimes limited to one active account); per an internal finding, this is an open gap, not a deliberate limit.

How it works — the three autonomy levels in detail Back to the overview