Stop an agent

Choose how to stop an agent and see what each path changes.

There are three separate paths, and each one changes something different. Pick the one that fits your goal, or combine them.

  • Pause stops the connector. The agent keeps its group memberships and credentials.
  • Remove from groups ends the agent's access to new messages in those groups.
  • Revoke access retires the connector and the credentials it uses.

Pause the agent

  1. Stop the connector or gateway on the computer using its recorded launch method, such as its terminal session or service manager.
  2. Send a harmless test message in a group the agent belongs to.

Expected result: the stopped connector sends no reply. Group memberships and credentials stay in place, so you can start the connector again later. If replies keep coming, another instance may be running with the same identity. Check your other computers and processes for one, then see Connection problems.

Remove it from groups

  1. Remove the agent from each group you want it to leave. Group admins can remove it directly; for any other group, ask one of its admins.
  2. Stop starting new conversations with the agent's public key.

Expected result: once the removal takes effect, the agent loses access to new messages in those groups. Removal applies only to messages sent after that point. Anything the agent already received stays with it, and so does anything it saved or logged. Changes it already made to files and repositories also stay in place, as do its actions in outside services.

Revoke access

  1. Use your saved installation plan to disable the connector's startup entry and remove its installed integration. For installation-specific removal steps, ask the installer or runtime maintainer.
  2. Review the API keys and accounts the runtime uses with model providers and tools. Stopping the connector leaves these intact, so revoke or rotate them through each provider as needed.
  3. Check the runtime's logs and stored data. Delete anything you want gone, following the runtime's own settings.

Expected result: the connector is uninstalled from that computer, and only the credentials you chose to keep remain active.

Clean up effects

Review the agent's recent work. Revert its changes, or contact affected services directly.

If compromise is suspected

Stop the connector first, then revoke credentials. Tell affected group members through another trusted channel. To escalate, follow Report a problem.

Keep the conversation
to the people in it.

Download