What's new in OpenTag

The standard Meeting prep routine now looks 90 minutes ahead instead of 45, giving it more time to research upcoming meetings and send your private briefing. Existing routines that still use the standard instructions receive the longer window automatically. Customized instructions stay unchanged, and paused routines stay paused. A related fix preserves organizer and attendee names from Google Calendar so OpenTag can use them in your briefing.

Fixed larger Gmail searches being rejected for requesting too many messages at once. OpenTag now reads them in smaller pages and can continue through the results. Google permission and quota errors also retain their actual explanation instead of incorrectly telling you the connection has expired.

Gmail approval cards now stay in the Slack conversation and thread where you asked OpenTag to send the email, including the message preview. A current workspace member with permission to send from that connected account can approve or decline, and the completed card shows who made the decision. Clicks from someone without access leave the request available for an authorized reviewer.

The status page now names affected integrations when connection renewal problems interrupt access, with observed failure and confirmed recovery times. Successful requests to other apps no longer hide an affected integration's problem, and incidents stay open until recovery is confirmed.

Enter your email on your phone to receive a setup link you can open on either your phone or computer. The link continues through Slack sign-in while preserving your invitation and chosen plan. Desktop sign-up continues directly through Slack, and returning users see a dedicated sign-in screen.

Name a model in your request to use it for that task without changing your workspace's chat default. Routines now have their own model setting and use Auto by default. OpenTag also handles obvious typos in model names and asks which model to use when it cannot match your choice, so you can clarify and continue the original task.

Routine owners can now approve actions such as sending email or changing calendar events for future runs, using a Slack approval card or the routine's settings. Each permission applies to that routine and the connected account shown, and you can revoke it at any time. Changing the routine's instructions requires approval again; previously skipped actions are not replayed.

When OpenTag cannot access a Slack channel, it now states that limit plainly without guessing that it needs an invitation or a settings change. It can also confirm that your settings remain unchanged, making it clearer what happened and whether there is a known next step.

Fixed signing in to a second Slack workspace with the same email address sometimes sending you back to your original workspace. OpenTag now opens the selected workspace's dashboard or setup flow, keeping each workspace's setup separate.

OpenTag can now query table data through a read-only Supabase connection, including totals, trends, and questions that combine multiple tables. You no longer need to grant write access for these reads. Existing read-only connections can use the new query capability while keeping changes to the database blocked.

Fixed a problem that could stop a working Sybill connection from accessing your calls when its sign-in needed to renew. Affected connections can now recover on their next automatic renewal without requiring you to reconnect Sybill.

Ask OpenTag to save a default parent page for new Notion documents, or name a page or teamspace for a single request. For team documents without a chosen destination, OpenTag now asks where to put them instead of silently creating a private draft. Sharing a Notion connection in OpenTag does not change who can open pages in Notion, so choose a destination shared with your intended readers.

Improved completion checks for routines instructed to stay quiet when there is nothing to report. OpenTag now better accounts for the run's timing and the information it checked, reducing cases where correctly sending no report was flagged as incomplete work.

Fixed scheduled routines being blocked from reading routine details and run history their owner is allowed to access. They can now use those reads in reports while respecting the report's audience: channel reports still require channel access, and private run details remain private. This does not give scheduled runs permission to edit or manage routines.

When a routine request leaves an important source or outcome unclear, OpenTag now looks up the named project or product and asks a focused question if needed before creating the routine. Follow-up answers are combined with your original instructions, including whose activity to watch and what to exclude. Clear requests can proceed without extra setup questions.

Fixed a problem that could cause OpenTag to miss requests in Slack Connect channels shared with another organization. Requests now reach the connected workspace correctly when Slack identifies the message's workspace differently, while keeping the channel's existing access and reply settings.

Fixed requests for an existing Slack file sometimes finding the file without sending it. When you ask for the file itself, OpenTag now delivers the original into your thread and links its filename directly to the delivered file, including filenames with parentheses. Requests for just a link, summary, or information from a file still return what you asked for.

Ask OpenTag to create a shared Slack List, add tasks with assignees and due dates, or work with a list already shared in your channel. You can keep checking tasks off yourself or ask OpenTag to enable automatic check-offs for that list. When enabled, OpenTag uses evidence of completed or reopened work to update existing tasks and posts a brief notice when their status changes.