The agent's Slack app, if the platform made one

The agent's live Slack app (creating, created or deleting), or null when it has none. Secrets appear only as whether each is stored; secrets.slack_bot_token.configured says whether Slack handed over a bot token; an install refused after the code exchange keeps it, so the agent's slack_bot identity is what says the app is installed. The install link comes from POST /v1/agents/{id}/slack/install/start. warnings says why every Slack mention and DM would be refused with a notice in the thread: no_active_release before an activation, profile_unavailable (with the profile_id) while the catalog no longer has the active release's profile, defines it otherwise than it was released, or an owner blocked it, and repository_required (with the profile_id) while a session cannot start: the agent has no settings row and its release names no repository its profile needs, or names one the profile or the workspace's repository ceiling does not allow, or the agent's GitHub settings cannot be read. Connecting is not blocked. config_token_issuer_changed (with the app's maker as previous_user_id and the token's issuer as user_id) says the App Configuration Token now belongs to another Slack user than the one who made this app, who may not be able to manage it or install it. config_token is the workspace's App Configuration Token state (unset, active, needs_reentry), readable here by the agent's admins too: only active can create the app, and only an owner or admin can set it. Owners, admins, the agent's admins and the live members of its managing team; API keys are refused.

Auth: cookie session only; no scope.