Goal for this release
The last release added important connectors, clearer access controls, and more reliable synchronization. It also showed us the next set of problems: Hyper could only use a limited part of many connected products, reviewing a long answer required repeated back-and-forth, multiple accounts were difficult to manage, and several parts of the app still felt unfinished.
Our goal for this release was to address those problems directly:
- Turn on Hyper’s new connector system and dramatically expand what the agent can do across connected products.
- Add the connectors needed for CRM, professional networking, databases, and meeting intelligence.
- Make it easier to review and revise detailed answers.
- Safely support multiple accounts from the same provider.
- Make connector actions and their permissions easier to understand.
- Bring Hyper to iPhone through TestFlight.
- Fix the UI issues and everyday bugs that made the product feel less polished.
Hyper’s new connector system is live
This release turns on the new connector system we have been building over the past several weeks.
Previously, many connectors exposed a small collection of tools that Hyper’s team had implemented individually. Even when a provider offered hundreds of useful API operations, the agent could only use the handful we had manually added.
The new system works from each provider’s native API definition. Depending on the product, that may be an OpenAPI specification, GraphQL schema, Google Discovery document, Swagger definition, or Model Context Protocol tool catalog.
Hyper compiles those definitions into a bounded interface the agent can search and use. This gives the agent access to a much larger portion of each connected product without requiring us to build every operation as a separate tool. (#325, #336, #363)
The system preserves each provider’s own structure:
- GitHub and Linear use their native GraphQL schemas.
- Gmail, Google Calendar, and Google Drive use Google Discovery.
- Attio, HubSpot, Jira, Confluence, PostHog, Stripe, Supabase, and other HTTP APIs use their native OpenAPI or Swagger definitions.
- Granola, Krisp, Neon, and Wispr Flow use their native Model Context Protocol interfaces.
- LinkedIn runs through a dedicated Unipile adapter that keeps account credentials and tenant details outside the generic connector runtime.
Before a request runs, Hyper validates the complete method, path, query, and body against the compiled interface. Requests that fall outside the authorized surface are rejected before credentials are loaded or a network request is made. (#344, #345)
Hyper also tries known requests directly instead of repeatedly searching an interface it already understands. When a provider rejects a request, the useful part of that error reaches the agent so it can correct the request without exposing internal database or infrastructure details. (#357, #372)
This is a major change to what Hyper can do. It also makes new connector capabilities much faster for us to ship: instead of creating an entirely new tool for every action, we can safely expose more of the provider’s existing API through one shared system.
Five new connectors
Hyper now connects to HubSpot, LinkedIn, Krisp, Neon, and Wispr Flow.
HubSpot
Hyper can now connect to a HubSpot portal and use its CRM alongside information from the rest of your company.
The connector covers HubSpot’s standard and custom CRM objects, including:
- Companies, contacts, deals, tickets, and leads.
- Notes, emails, meetings, calls, tasks, and messages.
- Quotes, products, invoices, payments, subscriptions, and orders.
- Lists, owners, pipelines, schemas, associations, and custom objects.
- Shared-inbox conversations.
Hyper stores records with the labels, properties, stages, and relationships defined by the connected portal rather than assuming every company uses the same CRM structure.
It can search and read records, inspect schemas and lists, create or update records, add notes, manage tasks, associate records, and archive records when explicitly asked.
HubSpot changes arrive through application webhooks, regular checks for recently modified records, and periodic full reconciliation. This combination covers property changes and custom object types that HubSpot does not expose through its webhook system. (#339, #359)
Hyper can now connect to a LinkedIn account through Unipile.
The connector can work with:
- The connected account’s profile.
- LinkedIn conversations.
- Connections and invitations.
- Companies and profiles.
- Posts and comments.
Hyper can search for people, inspect profiles and companies, read conversations, draft or send messages, send connection requests, publish posts, and comment on posts when asked.
The connection runs through a provider-specific security boundary. Hyper binds every request to the LinkedIn account that was connected and does not expose Unipile tenant credentials or account-routing fields to the agent. (#341, #354)
Krisp
Hyper can now connect to Krisp as a read-only meeting source.
It can:
- Search recorded meetings.
- Read meeting notes.
- Read transcripts.
- Find action items.
- List upcoming meetings when a calendar is connected.
Owned and shared meetings are indexed into the workspace. Hyper distinguishes between a meeting that does not exist, one that has not been transcribed yet, and one whose transcript was shortened because it exceeded the read limit.
A missing calendar or disabled provider setting is returned as something the user can fix rather than as an unexplained tool failure. (#342, #352, #397)
Neon
Hyper can now connect to Neon through Neon’s Model Context Protocol server.
The connector can:
- List the projects and branches an account can access.
- Inspect the databases on a specific branch.
- Address a project, branch, and database directly.
- Run bounded, read-only SQL queries.
Hyper does not rely only on the permission displayed by Neon’s consent screen. Queries are wrapped as a single read and executed inside a read-only transaction. Results are bounded before they enter the conversation.
Database credentials and connection strings are withheld from the agent. A database can still be addressed directly even when it falls outside a shortened browse result, so listing limits do not become access limits. (#340)
Wispr Flow
Hyper can now connect to Wispr Flow’s Notetaker and scratchpad.
It synchronizes:
- Recorded meetings.
- Flow summaries and personal notes.
- Decisions and action items.
- Full meeting transcripts.
- Scratchpad notes.
Hyper can search meetings and notes, read a meeting or transcript, list upcoming events, and resolve shared-note links.
Wispr Flow returns long notes and transcripts in character ranges. Hyper follows those ranges with explicit stopping rules, keeps the content in order, and marks a document when the provider stopped before the complete body was available. (#406, #409, #413)
Comment directly on Hyper’s answers
You can now review a Hyper response the way you review a shared document.
Select a passage in an answer, add a comment, and continue reviewing. Each comment appears above the message composer and is sent with your next message.
This makes it possible to review a long draft in one pass:
- Highlight one passage and request a change.
- Highlight another and explain what is missing.
- Add more comments wherever needed.
- Send everything to Hyper at once.
Each comment keeps the passage it refers to, what you said about it, and its position in the response. Comments are separate from file attachments, with their own count and size limits. (#380, #388, #392)
After a comment is sent, the passage remains highlighted and the comment appears on the message that carried it. Closing and reopening the conversation preserves both the comment and its relationship to the original passage. (#407, #411)
This is especially useful for emails, plans, product documents, investor updates, marketing copy, and other work where several parts of one answer need separate feedback.
Multiple accounts for the same connector
A member can now connect more than one account from the same provider.
For example, you can connect:
- A personal and work Gmail account.
- Multiple Google Calendars.
- Two Slack workspaces.
- More than one GitHub installation.
- Multiple accounts from another supported provider.
Each connection gets its own row in Settings. When several connections share a provider, Hyper uses the account name as the row title so they are easy to distinguish. Connect, reconnect, disconnect, and sharing controls apply to the exact row you selected rather than every account from that provider. (#360, #374, #382, #401, #408)
The account is also part of the authorization boundary. Hyper no longer selects an arbitrary connection when several accounts could satisfy a request.
When a request does not make the intended account clear, Hyper lists the available accounts and asks which one to use. It does not silently choose one. This is especially important for actions such as drafting an email, sending a message, or changing a record. (#368, #416, #419, #421, #423, #427)
Reconnects are also tied to the account they started from. If a provider’s consent screen returns a different account, Hyper rejects the renewal rather than updating the wrong connection and reporting success. (#390)
Connector actions have clearer permission controls
The new connector system distinguishes between reading information and performing an action.
Read-only operations can proceed without an unnecessary prompt. When Hyper wants to perform another kind of operation, it prepares and validates the complete request before asking for permission.
The approval card shows:
- The connector involved.
- The operation Hyper wants to perform.
- The permission being requested.
- Whether the approval applies once or can be remembered.
You can deny the request, allow it once, or allow the same operation in the future. Durable approvals are tied to the exact connected account and its current authorization. Reconnecting an account invalidates old approvals rather than carrying them onto a new credential. (#338, #343, #345, #346, #348, #351)
Approvals are stored with the conversation, so reopening a previous chat still shows what was requested and whether it was allowed, denied, or expired.
The same approval experience is now available on iPhone as well as desktop. (#378)
Tool activity is easier to follow
Hyper previously displayed every tool call as a separate card with technical fields that were difficult to scan.
Consecutive tool calls now appear as one activity timeline. While Hyper is working, the timeline shows short descriptions and the sources being used. Once the work finishes, it collapses behind a simple “Done working” summary.
Approvals remain visible outside the collapsed timeline because they require a decision from the user.
The timeline also uses the real connector mark for each source, provides clearer progress text, and avoids filling the conversation with raw request and response JSON. (#353)
The iPhone app now uses the same timeline, thinking indicator, provider marks, and approval states as desktop. (#378)
Files and pasted content are easier to work with
Attachments now keep one consistent appearance before and after they are sent.
Images, PDFs, documents, spreadsheets, and pasted text appear as artifact chips with the file name, type, and an appropriate preview. Sent attachments no longer change into a different generic tile after leaving the composer.
Images open in an image viewer. Text-based files and large pasted passages open in a readable text view. PDFs attached to a draft can be previewed in the app. (#361, #362)
Large pasted passages now become attachments instead of taking over the composer. Smaller pastes remain editable as normal message text. Pasted text also keeps its identity when a conversation is closed and reopened rather than returning as an unnamed file. (#362, #370)
Choose how Hyper responds
You can now set personal response preferences under Settings → You → Responses.
Preferences include:
- Length: Default, short, or very short.
- Formatting: Default, prose, or structured.
- Tone: Default, warm, or formal.
- Custom instructions: Up to 2,000 characters of additional guidance.
Changes apply automatically without a separate save button and sync across desktop sessions.
These preferences affect how Hyper presents its answer. They do not change which tools it uses, what evidence it considers, or which permissions an action requires. A member who leaves everything at the default receives the same behavior as before. (#417)
Hyper for iPhone is on TestFlight
Hyper is now available on iPhone through TestFlight, at https://testflight.apple.com/join/TCFSyRbj.
The iPhone app uses the same Rust core as the desktop app, giving it the same account, workspace, conversation, and connector state rather than maintaining a separate mobile implementation.
The app supports:
- Google and Apple sign-in.
- Onboarding and workspace switching.
- Conversation history.
- Streaming responses.
- Tool activity and source details.
- Connector approval controls.
- Model selection.
- Secure token storage in Keychain.
Sign in with Apple uses Apple’s native authorization flow and a nonce-bound identity exchange. Apple’s one-time profile name is saved before the account loads, so private-relay accounts do not have to appear under an unreadable email address. (#324)
Tool progress and approvals now match the desktop experience instead of appearing as incomplete mobile placeholders. (#378)
We also shortened the release path for both apps. Desktop and iPhone builds can now run in parallel, with dedicated caches for Rust and Xcode build output. This reduces the time between a finished change and a TestFlight or desktop build being ready. (#395)
Account and workspace settings now work completely
Several controls in Settings previously appeared interactive without saving the result.
Display-name changes now persist through the account’s identity record and appear in workspace rosters after the account reloads. (#389)
Workspace renames now remain visible after server refreshes and cannot be overwritten by an older list request that finishes late. (#399)
You can also upload an account photo. Hyper validates the actual image contents, removes embedded camera metadata, applies orientation, creates a square image, and stores the result under an immutable address. A photo you choose takes precedence over one supplied by the sign-in provider. (#405)
Workspace administrators can upload a workspace image as well. It appears in the sidebar switcher, workspace menu, and Settings. Private workspaces continue using their initials. (#425)
Chat and navigation feel more stable
We fixed several issues that made normal use feel rough.
Streaming no longer moves the page away from you
Scrolling upward while Hyper was answering could cause the transcript to pull itself back toward the newest message. Tool timelines opening or closing could also move the text someone was reading.
The transcript now distinguishes between following the latest response and holding the position chosen by the user. While held, it anchors the visible message as content grows or collapses around it.
Keyboard scrolling, small trackpad movements, scrollbar dragging, and the return-to-bottom control now behave consistently. The copy button also remains stable when a streaming response briefly pauses. (#369)
Signed-in users no longer see the sign-in screen flash
A returning user could briefly see the full sign-in screen while Hyper restored their existing session.
Session restoration now has its own loading state. An account that genuinely cannot load gets a separate screen with Try again and Sign out, rather than disguising recovery as another Google sign-in attempt. (#377)
Updates return Hyper to the foreground
After installing an update and restarting, Hyper could reopen behind other windows. The restarted app now focuses its main window immediately. (#337)
Connector settings are clearer
Each connected account has its own row, account names are used when a provider has several connections, and dialogs identify the exact account being reconnected or removed.
This removes ambiguous rows such as two connections both titled “Gmail” and prevents an operation on one account from making every account from that provider appear busy. (#374, #382, #408)
Synchronization is more resilient
We rebuilt significant parts of connector synchronization around durable jobs and explicit failure types.
A synchronization failure is now classified as one of several outcomes:
- Temporary: Retry with bounded exponential backoff.
- Rate limited: Wait for the provider’s requested delay.
- Unauthorized: Pause until the connection is renewed, with periodic recovery checks.
- Invalid: Stop the current scan and try again during the next scheduled pass.
Retries remain durable across server restarts. Webhook and operator requests are also stored before they are acknowledged, and repeated requests are combined instead of creating overlapping scans. (#379)
A shared worker pool now runs indexing across providers instead of relying on separate polling loops. Jobs from the same provider account respect one shared rate authority, while independent accounts can continue in parallel. A rate limit observed through one workspace therefore prevents another workspace from immediately repeating the same request against the same provider account. (#385)
The new indexing system now covers:
- Gmail messages. (#383)
- Google Drive and Shared Drive files. (#384)
- Notion, Attio, Jira, and Confluence. (#394)
- Granola and Krisp meetings. (#397)
- GitHub issues and pull requests.
- Slack channels, messages, and threads.
- Stripe customers, subscriptions, invoices, and refunds. (#404)
- Wispr Flow meetings and notes. (#413)
Indexing requests are checked against the same compiled provider interfaces used for interactive agent calls. A connector therefore cannot silently drift into making requests that its published contract no longer supports.
Provider API changes are detected before a release
Connected products change their API definitions independently of Hyper. A removed field or renamed operation could previously appear only when someone used that connector.
A scheduled connector-drift job now compares the live provider definitions with the immutable versions used by Hyper. It reports all changed or failed connectors in one Slack alert, with bounded diffs in the job summary and complete diffs stored as workflow artifacts. (#364, #365, #366)
Provider definitions are stored as immutable, content-addressed release objects rather than downloaded unpredictably during a release. A release therefore builds against the interface that was reviewed, while the separate drift job tells us when an upstream provider has moved. (#364, #367, #393)
What this release enables
The largest change in Hyper 1.4.0 is not any single connector or interface improvement. It is the new foundation underneath them.
- Hyper can use a much larger portion of each connected product’s real API.
- New capabilities no longer require a separate hand-built agent tool for every operation.
- Requests are validated before credentials or network access.
- Actions can be gated by explicit, reusable permissions.
- Multiple accounts can coexist without Hyper guessing which identity to use.
- Synchronization has durable retries, shared rate-limit handling, and one worker model across providers.
- Inline comments make long answers much faster to review and revise.
- The iPhone app makes the same conversations and company context available away from the desktop.
- The desktop experience is more stable, consistent, and complete.
This moves Hyper significantly closer to being an agent that can do real work across your entire company, not only retrieve information from it.
We are continuing to expand safe read and write support across every connector, make connector synchronization increasingly self-healing, and improve the agent’s ability to complete longer and more complicated work.
If there is a connector or workflow your team needs, tell us at founders@heyhyper.ai.