What's new in OpenTag

Workspace owners and admins can now view routines that deliver to Slack channels, including routines created in a private DM. Review their saved instructions and basic run history in the dashboard or ask OpenTag privately. Personal DM routines and private run details stay restricted, and editing still requires the appropriate permission.

Axiom

Connect Axiom to ask OpenTag about your logs, traces, and metrics, inspect dashboards, and check monitors. Sign in through Integrations and choose the access OpenTag should have. With permission to make changes, you can also ask it to create or update dashboards and monitors.

Fixed a problem where a retried routine run could prevent the next scheduled run from starting. Later runs can now proceed even when timing information from the previous run is unavailable.

Fixed unavailable Slack DM history being reported as an execution error when OpenTag simply could not access that conversation. OpenTag now treats this as an access limitation, without implying that no earlier messages exist.

Admins can now set reply and access defaults for groups of Slack channels and DMs in Slack settings. Existing and new conversations follow their group's defaults unless you have chosen a setting for that conversation. Individual choices stay intact when defaults change, and you can reset a conversation to follow its group again.

Admins now choose the model or Auto mode in one place in workspace settings. Web chats, Slack conversations, and routines use that setting when work starts or retries, replacing separate chat and channel selections. Queued work picks up your latest choice when it starts; work already running keeps its current model.

Meeting prep is now enabled by default in newly created workspaces. Once you connect your Google Calendar and OpenTag can message you privately in Slack, it can send briefings before upcoming meetings. You can pause it in Routines, and existing workspaces keep their current settings.

Ask OpenTag to also deliver an existing routine to another Slack channel. Each run produces one report and sends the same text and attachments to the channels you select, keeping the routine's schedule, instructions, and history together. Reports use only sources allowed for every destination, and you can add or remove channels as your audience changes.

Fixed service status measurements counting recovered attempts as failures or leaving gaps during busy periods. The status page now reflects verified final results and keeps periods without enough evidence marked as unmeasured. Supported website outage history also links to the related incidents, making it easier to understand past interruptions.

Linked citations now show source icons consistently beside their numbers throughout Slack replies. Slack messages and supported social sites have recognizable icons, while other websites use a globe. You can still hover over Slack message citations to preview the original message.

Admins can now choose how OpenTag responds in threads it has already joined, separately for each Slack channel. Keep Auto to let OpenTag decide when a follow-up needs its help, or choose @OpenTag only to require a fresh mention for each reply. Change the setting in the web app or ask OpenTag in Slack.

Fixed cases where an older connection check could overwrite an app's status after you reconnected or disconnected it. Status checks now reflect the current connection, including when an app renews its sign-in automatically.

OpenTag can now work on independent parts of a request at the same time and no longer stops solely because it has reached a fixed number of app or tool calls. This helps research and reporting tasks continue through the actions they need, while keeping dependent actions in order.

Fixed some model requests being counted as zero-cost usage despite consuming billable tokens. When pricing and usage details are available, OpenTag now estimates the cost using the model that handled the request. The fix applies to new requests; past usage totals are unchanged.