Connect AWS to ask OpenTag about your cloud resources and manage them within the permissions you grant. Guided setup helps you create an AWS role you control, without pasting access keys into OpenTag. Use the connection for requests and scheduled routines, with approvals for actions that change resources.
What's new in OpenTag
A running changelog of launches, integrations, and improvements. Updated most weekdays.
287 updates
October 2026
When OpenTag needs a missing detail or a choice, it now asks in its reply so you can answer with a normal message. You no longer need a separate question or confirmation card to continue the conversation. Approvals for actions still use their dedicated controls.
Team and Private sharing controls for custom MCP connections now apply to the workspace you are viewing. Changing sharing there preserves the connection's access in your other workspaces, making it easier to manage each workspace separately.
Fixed cases where OpenTag opened a PDF or text file during a task but missed its contents. It can now use those contents as the work continues. Files attached to your original request also stay with that request when you add instructions while OpenTag is working.
Connect Monaco to ask OpenTag about contacts, accounts, opportunities, tasks, and meetings. Prepare for a customer conversation by bringing together their deals, meeting details, and outstanding follow-ups. Choose Team or Private sharing and use a read-only connection when you only need to look things up.
Fixed scheduled reports requested "in this thread" arriving in a new direct message. When you explicitly ask for a report in the current Slack thread, OpenTag now keeps that destination for the scheduled delivery, including reports in channel threads and direct-message threads.
Fixed citations to Slack thread replies showing as unavailable or pointing to the thread's first message. Reply citations now open the specific message. Follow-up answers also avoid reusing citation numbers from an earlier answer, which could point to an unrelated source or appear broken.
Fixed usable app connections appearing under Needs attention solely because their credentials could not be verified. They now stay in Connected, with verification details available in the account view. Connections that need repair or renewal still show the appropriate warning.
OpenTag now checks pasted credentials with supported apps before saving a connection. If the app rejects your API key, the setup form explains the problem so you can correct it immediately. When the app cannot verify the key, OpenTag distinguishes that from a rejected credential.
Fixed app rate limits interrupting reports that need several reads, such as gathering notes from multiple Granola meetings. OpenTag now waits for the cooldown and retries supported reads automatically for up to six minutes, giving the request a chance to finish without asking you to start again.
With Circleback write access enabled, ask OpenTag to create or update action items, edit meeting notes, manage tags, and share meetings. Older connections may need reconnecting to grant write access. Circleback monitoring routines can also skip eligible checks when nothing has changed, while time-based reminders and digests continue on their saved schedules.
Fixed a problem that could leave OpenTag unable to open a Gmail attachment it had found, returning an email link instead of working with the file. Attachments found in messages, threads, drafts, and searches now include the information needed to download them from the correct connected account.