Goal for this release
This release brings a far more capable agent, eleven new connectors, conversation sharing, voice dictation, and Google Calendar, Sheets, and Slides editing.
Our goals were to:
- Let you redirect the agent while it works and queue follow-up requests.
- Keep work running and save progress independently of an open app.
- Make ongoing work, questions, and approvals available across devices.
- Connect more of your email, files, projects, meetings, and conversations.
- Make conversations easier to share, navigate, and continue.
- Fix performance and synchronization issues affecting everyday use.
A far more capable agent
Every Hyper app now uses the new agent runtime.
The agent runs on the server and saves progress between operations. Closing the app or losing the connection does not cancel accepted work. You can return to the conversation to review its progress and result. (#597, #613, #679)
Redirect the agent while it works
You no longer have to wait for a reply to finish before adding something important.
Send another message during a task to clarify the request, add context, or change direction. The agent incorporates it between operations rather than restarting the entire task. Calls already in progress can finish before the new instruction takes effect.
Your message can include text, pasted content, attachments, and comments on earlier answers. (#617, #618)
Queue your next request
You can also queue a follow-up to run after the current reply.
On desktop:
- Enter sends an instruction into the running task.
- Command/Ctrl + Enter queues a message for the next turn.
Queued messages can be edited, removed, or sent immediately while they are still waiting. Once accepted, they are stored on the server rather than depending on a local queue in the app. Editing or removing a waiting message cancels its saved entry before replacing it.
Delivery tracking also keeps an uncertain send visible instead of silently losing it or submitting another copy. (#622, #669)
Independent tool calls run in parallel
When a task needs several independent reads or actions, the agent can run up to four tool calls together instead of waiting for each one in sequence.
Completed results are saved separately. If you redirect the task, the agent stops starting additional calls from the old plan, lets active calls finish, and then applies your instruction. (#648)
Questions and approvals wait for you
Questions, connector approvals, confirmations, and reconnect prompts now save the pending work instead of holding an open execution session.
You can return later, answer the card, and continue from the saved step. These cards no longer expire simply because time has passed, though stopping the task, changing the request, or changing the relevant authorization can still invalidate them.
Existing approval requirements remain in place. Saving a task does not give it additional permission to act. (#671)
Stopping preserves completed work
Stopping a task now cancels server-side execution while keeping the partial reply and tool results already received.
You can review that work and follow up without starting from an empty conversation. An action already sent to another service may still complete; stopping the agent does not undo external changes. (#633, #662)
Work recovers from saved progress
Chat tasks and automation runs now use durable jobs with saved progress and explicit ownership of each running job.
After an interruption, the server can recover a saved model step or pending interaction. Tool calls whose outcomes are uncertain are not blindly repeated. This avoids treating a lost response as permission to send the same external action again. (#608, #686)
Active work stays in sync across devices
Open a conversation on another device to see its active work and pending questions or approvals.
The chat list reflects work started elsewhere, including new conversations whose first response is still running. Saved messages refresh during an active task instead of appearing only after it finishes. (#630, #631, #632)
Scheduled and event-triggered automations use the same new agent runtime. Existing automation definitions do not need to be recreated, and their confirmed instructions and action permissions remain in effect. (#668, #679)
Eleven new connectors
Hyper now connects to Outlook, Outlook Calendar, OneDrive, SharePoint, Microsoft Teams, OneNote, Asana, GitLab, Zoom, Loom, and Discord.
Supported actions follow each connector’s permissions and approval requirements. Provider plans, account roles, and organization settings can limit which features are available.
Outlook
Connect a personal, work, or school Microsoft account to:
- Search and read email.
- Create drafts and replies.
- Send and forward messages.
- Include chat attachments in supported email actions.
- Trigger automations from new email.
Mail is indexed with incremental updates and change notifications. Junk and deleted mail are excluded from indexing, and Outlook connections start private.
The initial attachment path supports files within Microsoft Graph’s inline attachment limit; larger uploads require a separate upload-session path. (#625)
Outlook Calendar
Outlook Calendar is a separate connection for:
- Finding events and recurring meeting occurrences.
- Creating and updating events.
- Accepting, declining, cancelling, or forwarding meetings.
- Checking availability and suggested meeting times.
- Triggering automations from new meetings.
Calendar synchronization follows Microsoft’s change feed. Events marked private or otherwise sensitive remain private in Hyper. (#657)
OneDrive
Connect a personal, work, or school OneDrive account to find files and use supported file actions.
Hyper indexes the contents of supported Word documents, Excel workbooks, PowerPoint presentations, HTML, and plain-text files. Other supported file records remain searchable by name and folder.
You can also upload a chat attachment or replace an existing file’s contents through supported actions.
Files available to anyone with the link or to the owner’s organization can be shared with the Hyper workspace, subject to the connection’s sharing setting. Other files remain private.
This initial version does not index PDF contents or files available only through “Shared with me.” (#695)
SharePoint
Connect a work or school Microsoft account to search:
- Document libraries and supported file contents.
- Lists and their populated fields.
- Published modern pages.
File and list updates use change feeds, while periodic reconciliation catches changes those feeds do not cover. Unpublished page drafts are not copied into the shared index.
The connector also exposes supported actions across SharePoint sites, lists, pages, and files. As with OneDrive, PDF contents are not indexed yet. (#674)
Microsoft Teams
Connect Microsoft Teams to search channel threads, chats, and available meeting transcripts.
Standard channel threads can be shared with the workspace. Private and shared channels, chats, and meeting transcripts remain private in Hyper.
The connector also supports Microsoft Graph operations for teams, chats, meetings, and related resources.
Teams requires a work or school account and organization administrator consent for the requested channel-message access. Transcript availability also depends on the organization’s settings. (#696)
OneNote
Connect a personal, work, or school Microsoft account to search the text of your OneNote pages, with their notebook, section group, and section.
Pages in a notebook you have shared can be shared with the workspace. Pages in other notebooks remain private, and OneNote connections start private.
Synchronization checks for changed sections and reads only the pages that changed. Page deletions are picked up during full reconciliation.
The agent can read notebooks, sections, pages, and page content. Creating new pages is not included in this release. (#715)
Asana
Connect Asana to search:
- Projects, sections, status updates, and briefs.
- Tasks, comments, attachments, and subtasks.
- Portfolios and goals.
Incremental synchronization and webhooks keep changed records current. Where an Asana plan does not include task search, synchronization falls back to project task listings.
Supported API actions let the agent update work in Asana, subject to your permissions and approval. (#661)
GitLab
Connect GitLab.com to search issues, merge requests, comments, and wiki pages from projects you belong to.
Pasted GitLab links can resolve directly to indexed issues, merge requests, and wiki pages. Confidential issues remain private.
The connector exposes supported GitLab API operations and uses project webhooks where the connected account has sufficient access.
Self-hosted GitLab is not included in this release. (#655)
Zoom
Connect Zoom to search hosted meetings with available summaries, cloud recordings, and transcripts.
The connector brings together the information available for each meeting, rather than treating its summary and recording as unrelated records. Meetings without a summary or recording are not included in this initial index.
The agent can also use supported Zoom Workplace operations across meetings, chat, calendar, and other services available to the connected account. Account-admin-only operations are not included. (#626)
Loom
Connect Loom to search owned and shared videos, including available:
- Transcripts.
- Comments.
- AI briefs.
- Action items.
- Related links.
The connector uses Loom’s tools through Atlassian’s interface. Supported writes require approval for each call. Transcript and download availability depend on the Loom plan and the provider’s permissions. (#627)
Discord
Install Hyper’s bot in a Discord server to search accessible channels and threads and use supported messaging actions.
Each connection is bound to one server. Requests for channels in another server are refused, even if the bot is installed there too.
Discord writes require approval for each request and remain limited by the bot’s role permissions. Synchronization uses polling; edits and deletions are picked up during full reconciliation rather than through live message events. (#628)
Share conversations
Use Share → Create link in a conversation to create a read-only copy that someone else can open in their browser.
The shared copy includes the conversation’s messages, tool activity, and comments. Questions and approval cards show their saved state without controls for the reader to act on them.
Each link captures the conversation when you share it. Later messages do not update that copy; create another link to share a newer version.
Anyone with the link can read the shared conversation without signing in. Review the contents before sharing sensitive information. (#675, #693, #699)
Shared-chat pages follow the reader’s light or dark appearance setting. Share tokens are removed from analytics URLs, and session replay is disabled on shared conversations. (#713)
Voice dictation
You can now dictate requests in the desktop composer.
Click the microphone and speak. A live transcription and input-level indicator show what is being captured. Choose Done to insert the transcript into your draft, then review or edit it before sending. Cancel discards the dictation.
Audio is transcribed through Deepgram. (#638)
Under Settings → Account → Dictation, choose the microphone the app should use.
The preference stays on that computer. If the selected microphone is disconnected, dictation falls back to the system default rather than failing. (#666)
Edit Google Calendar, Sheets, and Slides
The Google editing capabilities previewed in the previous release are now enabled for stable builds.
You can ask the agent to:
- Create and manage calendar events.
- Edit existing spreadsheets.
- Revise existing presentations.
Reconnect Google Calendar and Google Drive to grant the new permissions. Existing connections do not receive the additional access automatically.
Editing remains subject to the applicable approval requirements. (#619)
Existing connectors can do more
We expanded the permissions requested by Slack, Confluence, Attio, Supabase, Airtable, Krisp, Logfire, and PostHog.
This exposes more of the operations supported by each service. For example, Slack’s expanded interface includes additional operations for files, pins, reactions, reminders, conversations, and profiles.
The expanded permissions do not override provider plan restrictions or administrator-only access. Actions remain subject to their approval rules.
Reconnect existing accounts to grant the additional permissions. (#629, #644)
Reconnect accounts directly from a conversation
When a provider refuses a connection during a task, the agent can now show a Reconnect card at the failed request.
The card identifies the affected account and offers:
- Reconnect: Sign in again and retry the request once.
- Skip: Leave the connection unchanged and retain the original failure.
The retry uses the renewed authorization for the same account. This recovery card is for interactive conversations; unattended automations do not assume someone is present to sign in. (#659)
Long conversations are easier to navigate
Conversations with at least two sent user messages now show a navigation rail beside the transcript.
Hover over a marker to see its message label, then select it to jump directly to that turn. The rail supports keyboard navigation and scrolling with a mouse wheel or trackpad.
After a jump, the conversation holds your selected reading position while new output arrives. Returning to the newest message resumes following the live reply. (#652, #681)
Performance and synchronization fixes
Reduced memory growth during streaming
We fixed a desktop issue that caused memory use to grow rapidly while replies streamed and remain high afterward.
The app now sends small state-change notices and retrieves the current state when needed, rather than embedding the entire conversation in every update event. This removes the repeated retention of large chat payloads without changing how replies appear. (#724)
Faster connector status
Loading connection status no longer joins every indexed file into a large intermediate result just to count files per connection.
In the production query-plan check recorded with the change, a workspace with 78,535 files went from roughly four seconds to 42 milliseconds. Exact file counts and other status information are preserved. (#720)
Large Linear and GitHub discussions no longer block synchronization
A Linear issue with more than 100 comments, or a GitHub record with additional pages of nested results, could repeatedly stop synchronization.
Hyper now follows the remaining pages before publishing the record. This covers:
- Linear issue comments.
- GitHub labels and issue comments.
- Pull-request reviews.
- Review threads and comments within them.
Records are stored only after the required pages are complete, rather than silently publishing partial content. (#723)
Other additions and improvements
- Connector search: Find connected accounts and available connectors from the Settings search bar. (#621)
- Settings shortcut: Open Settings with Command +
,or from the Hyper menu on macOS. (#665) - More consistent streaming scroll: The conversation continues following a reply until you scroll away. (#609)
- Newline fix: The first Shift + Enter now visibly creates a new line in the composer. (#607)
- Restored pasted-text previews: Saved pasted content keeps its readable preview when you reopen a conversation. (#667)
- Clearer pending inputs: Delivered messages no longer remain visible as duplicate pending controls. (#669)
- More consistent styling: Refined sidebar group labels, pending-message actions, and neutral tool feedback. (#645, #663, #664)
- Support page: Added a dedicated support page. (#672)
The iOS composer-state fix also shipped in 1.6.1 and is included for anyone upgrading from 1.6.0. (#603)
Engineering and release improvements
We separated agent execution, connector services, and shared interaction cards into dedicated libraries. The server still owns application-specific APIs and conversation storage, while the extracted components keep their existing authorization, saved-state, and transaction contracts. (#717)
We also reduced the command-line tool’s cold build time. In the recorded M5 measurements, a fresh build went from 3 minutes 52 seconds to 58 seconds by removing unnecessary dependencies from the default build and compiling specialized commands only when needed. (#719)
These changes support faster development and releases; they do not change the permissions granted to the agent.
Coming next
- Hyper for Windows: We’re preparing the desktop app for Windows. Build, packaging, and update work is underway, but Windows is not included in this release.
- Cloud computer use: Have the agent write and ship code or do other work beyond connected APIs, including from your phone. The execution and file-transfer groundwork is in place, but cloud computer use is not enabled in this release.
- Inline generated interfaces: Task-specific interfaces directly in the conversation.
Have a feature your team needs? Tell us at founders@heyhyper.ai.