Goal for this release
The last release gave us the minimum foundation needed to put the rebuilt Hyper in users’ hands. Our goal for this release was to do that: onboard real users, watch where Hyper failed in daily work, and quickly improve the product around them.
We shipped 121 pull requests across five major areas.
Hyper can complete work
Finding the right information is often only the first step. Users still need to turn it into an email, document, task, or product decision.
Hyper can now create and safely update work in the tools teams already use:
- Create and edit Gmail drafts without sending them or overwriting newer edits. (#180)
- Create and update Linear issues. (#204)
- Create and edit Notion pages and database entries. (#205, #210)
- Create and edit Google Docs. (#115, #211)
- Read live PostHog analytics, annotate charts, and update existing feature flags when explicitly asked. (#242, #251)
Hyper reads the latest version before editing and refuses to overwrite work that changed unexpectedly.
We also added support for attaching Microsoft Word documents to a conversation. (#267)
Teams can onboard and work together
Getting Hyper to users required more than sending them a download link. Teams needed a complete path from creating a workspace to inviting coworkers and connecting their tools.
New users now create and name a workspace during onboarding. Workspace admins can invite people by email, assign roles, view or cancel pending invitations, and manage existing members. Invitations work for both new and existing Hyper accounts. (#154, #244, #247, #248, #254)
We also fixed a problem that could open an invited user in the wrong workspace and brought account, workspace, member, invitation, and connector settings into one clearer experience. (#259, #262)
Chat is faster and easier to follow
Users can now move between conversations or start a new one while Hyper continues working. Each conversation keeps its own draft, progress, response, and cancel control. (#237)
When Hyper uses a previous conversation, it shows that conversation’s name and lets the user open it directly. New conversation titles also appear immediately instead of after several delayed checks. (#203, #206, #213)
Connected information is more reliable
The first onboarding sessions exposed several places where connections could appear stuck, finish without updating the interface, or lose progress during a large import.
Connector status now updates immediately, shows clearer states and errors, and cannot be replaced by an older response that arrives late. (#208, #225, #228, #266)
We also made large Gmail imports resumable, added Google Shared Drive synchronization, and made Granola imports less likely to duplicate or lose meetings after an interruption. (#155, #212, #215)
We can learn from real usage
We added analytics for the rebuilt app so we can measure the path from opening Hyper to signing in, completing onboarding, connecting a service, and sending a message. Website activity can also be connected to the same user after sign-in. (#224)
Tracking began on August 13. In the first two days:
- 15 people opened Hyper.
- 10 completed onboarding.
- 7 connected at least one service.
- 11 sent 165 messages across 48 conversations.
Those numbers include internal and test activity, but the usage has already uncovered important problems. Users found cases where Hyper could not open a connected Google Drive file from its URL, missed new Gmail messages, or presented an older source too confidently when newer information existed.
We also made releases faster to build and added automatic Slack notifications when a deployment succeeds or fails. This helps us respond to feedback and ship fixes more regularly. (#200, #220)
What this release enables
In the last release, we wrote:
The next step is to onboard users, watch where the product fails in daily work, and improve it through regular stable releases.
We accomplished the core of that goal. People are now onboarding, connecting their tools, sending messages, and giving us specific feedback from real work. Hyper can also carry more of that work through to completion instead of stopping at an answer.
The product is still early. Our next step is to continue onboarding teams while improving the parts of the experience that now create the most friction:
- Make Google Drive files available through direct links.
- Fix missed Gmail updates and support drafting replies in existing threads.
- Make connection progress and app updates clearer.
- Fix remaining model and message failures.
- Improve source dates, version awareness, and confidence around conflicting information.
- Tighten connector access controls and continue expanding the actions Hyper can safely take.