Hover/Tag

Supported capabilities

Check which Slack and agent capabilities are supported, experimental, or unavailable in v0.2.0.

This page separates what Tag implements today from optional, experimental, or unavailable behavior.

Slack experience

CapabilityStatusNotes
Respond to app mentionsImplementedThe caller must be in SLACK_ALLOWED_USER_IDS.
Read the current threadImplementedTag fetches one page containing up to 30 messages.
Read supported attachmentsImplementedText content is truncated at 12,000 characters per item; downloaded image or text files are limited to 15 MiB.
Stream answer textBackend-dependentClaude streams text deltas; Codex App Server streams final-answer deltas and observed activity.
Continue with thread contextImplementedA later mention receives the current bounded thread context.
Post a requested top-level messageImplementedRestricted to the channel that invoked Tag.
Create a requested Slack CanvasImplementedRequires the Slack Canvas scope and explicit user intent.
Upload generated images as resultsNot implementedThere is no dedicated result upload-and-attach path.

Agent work

CapabilityStatusNotes
Codex CLI backendSupported pathUsed by the v0.1 launch qualification.
Claude Code backendExperimentalRequires an authenticated local Claude CLI session.
Inspect and change workspace filesImplementedUses the permissions of the backend process.
Run workspace commands and testsImplementedAvailable when the selected backend can perform them.
Use installed local tools and skillsAvailableEach tool uses its own credentials and grants.
Choose Codex model, reasoning, and Fast Mode per userImplementedSaved choices follow the user across channels and threads; operators can restrict model and reasoning choices.
Stop an active Codex turnImplemented with App ServerSlack's native Stop button interrupts the active turn; the legacy exec transport remains a rollback path.

Context and memory

CapabilityStatusNotes
Search allowed MFS scopesImplementedMFS_ALLOWED_SCOPES limits the bundled search helper.
Reopen precise MFS recordsImplementedRead and list helpers enforce the configured roots.
Use indexed Slack channel historyImplementedRequires a configured MFS Slack connector and an allowed slack:// root.
Use repositories, documents, issues, databases, and object storesConnector-dependentThe source must already be indexed by MFS and permitted to Tag.
Automatically remember every conversationNot providedContinuity comes from Slack threads, workspace state, and approved indexed sources.
Dedicated local memory-note storeNot providedDurable retrieval uses indexed, permitted MFS sources.

Operator controls

CapabilityStatusNotes
Owner accessSupportedConfigure the owner's Slack member ID during setup.
Multi-user accessComing soonAdditional callers are not part of the supported product flow yet, although the underlying allowlist accepts multiple IDs.
Explicit channel restrictionImplementedConfigure SLACK_CHANNEL_IDS; the bridge fails closed without selected channels.
MFS retrieval rootsImplementedConfigure MFS_ALLOWED_SCOPES.
Backend timeout and retry settingsImplementedConfigure the corresponding OPENTAG_ settings.
Organization-wide administration and approvalsNot providedThese remain outside the current reference implementation.

For the full end-to-end behavior, see Connected user flows. For configuration and exact backend commands, use the Slack adapter and backend reference.

Last updated

On this page