Skip to content
Hussh
Connect MCP

Release Notes

The public record of what shipped to hushh.ai and when, kept alongside the releases page on the site so users, the team, and the community read the same account.

Project1 weeks ago

TL;DR: Every release is documented in two places by principle: the releases page on hushh.ai and this page. This record begins 2026-09-11 with the careers release, and the full dated history back to the beginning lives on the site. The latest entry, 2026-09-28, rewrites One Engine in plain words, makes the legal pages scroll like a document, and renames the Glossary to the Guide with PCHP in it.

Status as of 2026-09-28: see body.

Building in the open means a release is written down where anyone can read it, not announced once and forgotten. Our engineering contract makes that a rule: every release is documented twice, on the site and here, the same day.

This page starts on 2026-09-11. The rule had been in place since 2026-08-27 and no page existed, so rather than backfill an account of releases from memory, it begins here, and the complete dated history stays where it has always been generated from the commit history: the releases page on hushh.ai.

2026-10-01 — Careers: apply however you keep your resume, and a hiring console that shows everything

A production release to hushh.ai and careers.hushh.ai. Pasting a resume now works when applying. The hiring team can see everything a candidate sent. And the careers connector for agents is limited to verified @hushh.ai accounts.

Said plainly: pasted resumes were being refused

On careers.hushh.ai, anyone who chose "Paste the text" for their resume was told a resume was required and could not apply; only a link worked. The form sent the text in a place the server did not look. That is fixed and was checked live after the release by applying with pasted text. Attaching a file had the same fault plus a second one (the server could not sign an upload address on our cloud); both are fixed and proven end to end on the test site. File upload is not switched on for applicants yet.

Everything a candidate sent, in one place

The hiring console now shows every detail an applicant submitted: contact details, profile links, what they wrote, the pasted resume or an Open resume button for an attached file, scorecards, the history of every change, and other applications from the same person. Opening a resume uses a short-lived private link and is logged. Every admin page now has Postings and Applications tabs, who you are signed in as, and Sign out.

The careers connector is for @hushh.ai only

careers.hushh.ai/mcp lets an agent such as Agent One list roles and, for the hiring team, work the pipeline. Every call now needs a sign-in that Google has verified for a @hushh.ai address. Nothing is open anonymously, and a candidate's private status link is refused outright.

Verified in production

Checked live after the release, not from a build log: careers.hushh.ai served the exact image tested on the test site, a pasted-text application was accepted, the headline and icons were in place, the admin pages asked for sign-in, and the connector refused a request without one.

2026-09-30 (evening) — For Defense, one tap to sign in, search that opens Agent One, and a lighter site

A second production release went out on the evening of 2026-09-30. A plain page for defense, honest about what we hold. The account icon now signs you in. The search button opens Agent One. Building in the open says who pays and how, in fewer words. Tag One shows the three features we are designing. And twenty older pages are gone, each forwarding to where its reader belongs.

For Defense, in the For Business menu

A short For Defense page sets out what Agent One, Puppy One and PCHP offer, and where we stand: FedRAMP High, DoD Impact Levels and CMMC are all in pursuit, and there is no authority to operate yet, so official and mission use waits for one. It names no partner, office or deal. The old /one/defense address now forwards here.

The account icon signs you in

On every page the account icon now leads to sign-in with Google or Apple, instead of the download page. Signed out, your profile shows the same two buttons the header menu does; once signed in, you land on your profile.

Search opens Agent One

The search button, in the header and in the phone tab bar, goes straight to the Agent One app. The old search page was retired; links to it forward to the app and carry the question with them. The question in the address is hidden from analytics there, as it was on the old page.

Building in the open, plainer

Building in the open now reads in three parts: who pays, what is hard, and where to check our work, closing with the site footer, which the page had been missing. The "Open One in your browser" section from the retired download page now sits on the Agent One page.

The three features we are designing for Tag One

The Tag One page gained one slide: life signs, not just location; SOS to the closest helper; and closeness by consent, each with one line on what an AirTag cannot do. All three are marked in design, and Tag One is described as a safety and wellness wearable, not a medical device.

Twenty older pages retired

The last-mile pilot plans, the Dog Tag pages, the Tag One guide and research, Garage One, and nine older One pages (proof, category, what's new, start, download, name your One, and three early app pages) were removed. Every old address forwards permanently to the page that now covers it, and links across the site were updated. The KYC agent page now says its early app flow is retired rather than available.

Said plainly: CI ran after the merges

To move quickly, these changes were merged before their automated checks finished. Before production, the full check suite was run on the exact code being shipped, and it passed. Separately, the Careers step of the staging deploy now skips itself cleanly until a pending permission is granted, instead of marking every staging build as failed.

Verified in production

Checked live on hushh.ai after the release, not from a build log: the account icon pointed to sign-in, the For Business menu linked For Defense, the Defense page served with every certification marked in pursuit, Building in the open carried its new headline and footer and no longer linked the retired page, the Tag One and Agent One pages carried their new sections, the search button pointed to the app, and all twenty-one retired addresses, the old search page included, forwarded to their intended pages.

2026-09-30 — Choose who can find you, the press kit gets the logos, and Careers gets its own home

Two production releases carried six changes, the second going out on 2026-09-30. You can now switch on, one detail at a time, what people may search you by. The brand kit moved into the press kit. Pages that snap from section to section now fit the screen. Building in the open joined the Guide and says it plainly. And every Careers link on hushh.ai now lands on careers.hushh.ai.

Find me: opt in, one switch at a time

Your profile has a Find me section. Each detail, such as an age band, sex or ZIP code, has its own switch, and every switch starts off. A detail left off is stored as unknown, so no search can filter a person by it. Only adults can turn it on, the age band and sex are worked out on the server rather than taken from the browser, and only a five-digit ZIP code is kept. Searching for people is not built yet, and the Your information page still marks it in design.

Logos and colours are in the press kit

The brand page folded into the press kit: the logos as SVG downloads and the palette with its values, next to the fast facts and the media contact. The old /brand address redirects there.

Every section fits the screen

On pages that snap from section to section, each section now lands just below the menu bar instead of under it, and the footer can be read in full. Measured live on the home, Puppy One, Tag One and One pages at a desktop size: every section and footer fit. The top section of the One Engine page is still 35 pixels taller than the screen.

Building in the open, rewritten and in the Guide

Building in the open now says it in three parts: how we make money (never your data), what is hard and what we do about it, and where to check our work. It sits in the Guide menu. The research hub page was retired; the papers stay at /research/papers.

One place for press

The Newsroom page and its footer link were retired, and /news now redirects to the press kit. The fact sheet and investor relations pages stay where they were.

Careers lives at careers.hushh.ai

Every Careers link on hushh.ai, including open roles, the role catalog, saved job links and old apply links, now forwards to its page on careers.hushh.ai, keeping any query string. The handbook and how-we-work pages stay on hushh.ai, because the careers site has no equivalent.

Verified in production

Checked live on hushh.ai after the release, not from a build log: /brand, /news and /research redirected to their new homes, the press kit carried the brand section, the fact sheet and the papers returned successfully, the homepage no longer listed Newsroom and did list Building in the open, the Careers paths forwarded to careers.hushh.ai with their query strings, and the handbook and how-we-work pages still served. The checks from the two previous releases were run again and still passed, including Find me refusing anyone not signed in.

2026-09-29 — Only you can read your profile, One Engine moves in with Puppy One, and Tag One takes a waitlist

One production release went out on 2026-09-29, carrying five changes. A new page explains your information in one sentence: your name shows, everything else stays behind a bar until you say yes. One Engine now lives with the Puppy One it runs on. PCHP says less and shows more. Tag One has a waitlist. And the Terms of Use read like the Privacy Policy.

Only you can read your profile

A new page, Your information, and a new homepage section show a profile the way a stranger sees it: the name, then gold bars over everything else. It says plainly what we can and cannot see, stated from the code rather than the pitch: the contents of a profile are encrypted on the person's device, while the names of its sections, how many details it holds and when it was last updated are readable on our side. Finding people and asking for details are marked in design on the page, because they are not built yet.

One Engine now lives with Puppy One

The One Engine page moved to /one/puppy/engine, next to the machine it runs on, and the old address redirects there permanently. The Puppy One page gained the AI Factory section (by day it is yours, overnight it helps out, by morning you earn), and the homepage no longer repeats it. The One Engine demo also lost its technical device readout.

PCHP in four steps, not nine sections

The PCHP page now reads in a minute: prove who you are, agree what is shared, share one field, keep a receipt, then four one-line promises. The card grids, the numbers wall, the economics section and the FAQ were removed; the long-form detail stays in the specification.

Join the Tag One waitlist

Tag One cannot be ordered yet, so the top of the Tag One page now takes an email address in place of a link to Agent One. Signups are stored through the site's existing waitlist, marked as coming from Tag One.

The Terms read like the Privacy Policy

The Terms of Use now use the same plain layout as the Privacy Policy and Your Data Rights. Every clause is unchanged word for word, which was checked against the previous page. Two links that led nowhere, "Archived versions" and "Download PDF", were removed. Data Ownership was also taken out of the Guide menu, since the Privacy Policy covers it.

Verified in production

Checked live on hushh.ai after the release, not from a build log: One Engine served at its new address without the readout, the old address answered with a permanent redirect to it, the Puppy One page carried the AI Factory, the homepage carried the Your information section and no longer the AI Factory, the PCHP, Tag One, Terms, Releases, Privacy, Data Rights and Field Guide pages all returned successfully with their new content, and the Guide menu no longer listed Data Ownership. The Tag One waitlist form was checked for presence, not submitted, so that no test signup was stored.

Two production releases went out on 2026-09-28. The page that explains One Engine was written for engineers; it is now written for anyone. The legal pages stopped snapping one section at a time. And the Glossary became the Guide, with PCHP in its menu.

One Engine, explained in three plain steps

The One Engine page used to talk about placement lanes, silicon and thermal budgets. It now says what happens: One Engine checks your device, reads the task, and sends it to the best place, your device, the cloud, or a bit of both. A small demo lets a reader tap an everyday task, like replying to a text or making a video, and see where it would run and why. The stat wall, card grids and jargon were removed, and the headings were made smaller.

A site-wide script turned any page with several sections into full-screen slides. On a legal document that meant fighting the page to read a clause. Privacy, Terms and Your Data Rights now scroll normally, like the paper they replace.

The Glossary is now the Guide, with PCHP in the menu

The menu that held the Glossary is now called Guide, in the header, the mobile menu and the footer. Next to A-Z, Consent & Privacy and Data Ownership it has a link to PCHP, the open protocol behind every consent request and receipt.

Said plainly: the first attempt to publish stopped halfway

The first production run stalled when the cloud did not bring up the new backend server within its deadline, so the new pages did not go out. The live site kept serving the previous release the whole time and nothing went down. The backend came up on its own shortly after, and a second run published the pages cleanly.

Also in these releases

A fix to the automated checks that every change must pass, which had been failing for every pull request after an earlier change. The 2026-09-27 releases (plain legal documents, the Devices pages and the Field Guide) are listed on the releases page and are not yet written up here.

Verified in production

Checked live on hushh.ai after each release, not from a build log: the One Engine page served its new content with the old headline gone, the slide script skips the three legal pages, the Guide menu with its PCHP link appeared on the React pages and the Field Guide, and the home, One, Puppy One, PCHP, Field Guide, Data Rights and Privacy pages all returned successfully.

2026-09-26 — University pages written for the people on campus

Every university page on hushh.ai was rewritten for the faculty, staff and students deciding whether to work with us: what we work on, who to know, and how to start.

What we work on, in order

Three focus areas, written as questions a professor or a student can pick up: private AI infrastructure for people, turning a person's attention, time and preferences into a private agent that manages their context across every agent that wants to know them, with their consent; permanent asset management and quantitative strategies, as research only and never an offer or investment advice; and personal supercomputing.

People to know, and students we would love to meet

The University of Washington page features key UW faculty whose public work aligns with ours, each described from and linked to their own university page. Being listed does not mean someone works with us or endorses us, the page says so beside the list, and anyone can ask to be removed. Students are never named; instead each page describes the PhD, Master's and MBA students we hope will write to us, and what they would work on.

What we no longer publish

Public pages no longer describe the stage of any university relationship or what it costs. University Relations shows one alphabetical list of the universities we work with, and the research lab pages no longer carry agreement amounts or status labels. Those details belong in conversations with each university, not on a web page. The word partner stays reserved for executed agreements.

Also fixed

The machine-readable summary we publish for answer engines had listed two universities we work with in India under the wrong heading. It now reads from the same list as the pages, and an automated check fails the build if the two ever disagree. A test that had been failing on the main branch since a favicon change was brought up to date.

Verified in production

Checked live after the release: every university and research lab page returned its new content with no status labels, amounts, or fund references, the UW page listed its featured faculty with their sources, and the answer-engine summary matched the pages.

2026-09-25 (later) — A page for the University of Washington

A first page for the University of Washington went live, setting out two research directions and paid work for UW students fifteen minutes from our Garage in Kirkland. It was rewritten the next day, above.

2026-09-25 — Careers gets its own front door, and universities get an honest list

Applying, checking on an application, and hiring now all live on careers.hushh.ai. A new page sets out how we work with universities, naming only the ones we have signed with as partners. And the application email an earlier release admitted had never sent has now been watched leaving the building.

The application email is proven, not just configured

On 2026-09-11 we said no application email had ever sent, and that we would not claim otherwise until we had watched one go. We have now. A test application on our staging system produced all three messages, the receipt to the applicant, the note to the hiring team, and the support copy, and our own logs recorded each one as sent. That code shipped to production in this release. The first real application there is the next one we will watch.

Your status page moved, and your old link still works

The page where a candidate checks their stage, withdraws, or deletes their application now lives at careers.hushh.ai/status. Anyone holding a link from an earlier email is forwarded there with their private key intact, so nothing already sent stops working. The hiring team's tools moved to the same host, behind a sign-in that is checked before any page is sent.

A closed role now says it is closed, everywhere

Job pages are built ahead of time for speed, which meant a role we had closed kept its page on the careers host and kept inviting applications. Closing a role now takes its page down straight away with an honest answer, 410 Gone, and tells search engines to drop it. This was proven on staging by closing a real posting, watching its page change within a minute, and reopening it.

University relations

A new page, University Relations, explains how we work with universities: research, students, and the neighbourhoods we live in, with schools near our offices we would love to get to know. It was rewritten on 2026-09-26, above.

What else rode along

This release also carried twenty changes other teams had merged since the previous production release on 2026-09-18, among them the redesigned homepage, plain-language rewrites of the Agent One, Devices, Pricing, Company and Glossary pages, and the Shopify catalog on the shop page. Each passed the same automated checks on its own pull request; the full list is on the releases page.

Verified in production

Both hosts were checked live after the release, not from a build log. Every new page returned its expected content, the old candidate link forwarded with its key, the admin pages refused anyone not signed in, and the compliance page still read "in pursuit" for certifications we do not hold. Production has no closed roles, so no live job was affected by the new closed-role behaviour.

2026-09-11 (later) — Nine cities, an honest answer about remote, and what the job pays

Every one of the 129 jobs is now open in San Francisco, Palo Alto, Seattle, Kirkland, Austin, Dallas, Chicago, Miami and New York, and every posting says what the job pays and what comes with it.

The remote claim was wrong, and then wrong the other way

Before today, 125 of the 129 postings told Google the job was done entirely remotely. It was not. That put office jobs in front of people searching specifically for remote work, who would have found out on arrival that the role is five days in a building. Nothing errored; the claim was simply untrue, and untrue claims that produce no error are the ones that last.

The first correction over-swung and marked everything office-based, which was untrue in the other direction, because the customer-facing roles genuinely are remote.

Where it landed matches how the company actually works. Forty roles are remote-friendly: sales, field work, client service, partnerships, and forward-deployed engineering. Those people can be based in any major US city with strong domestic and international airport connections, because the job is being where the customer is. The other eighty-nine are office-first across the nine cities, five days together, and remote-friendly around family arranged one person at a time, which we would rather people used than toughed out.

Where a category was genuinely ambiguous it was left as office-first. Telling someone a job is remote when it is not costs them a great deal more than the reverse.

What comes with the job, on every posting

Indicative pay ranges by market and level, published openly. Stock options for every full-time teammate. An annual bonus, or on-target earnings with uncapped commission for customer-facing roles. Medical, dental and vision for you and your family, plus life and disability cover, on the highest plan tier available to us. A 401(k) with company matching. A budget of AI tokens of your own, because a company that says you should own your AI cannot be the company that rations it. A gym membership and real retailer discounts. And the referral kicker.

What these postings deliberately do not say

No 401(k) match percentage, no premium share, no deductible, no waiting period. The benefits platform and the plan tier are decided; those specific numbers are not, and a job posting is something a person leaves a job on. They will be in an offer letter before anyone signs one. A test fails the build if any of them ever appears in a posting before then.

Verified in production

All 129 postings checked live: every one carrying the nine cities, the pay and benefits, and the working policy that actually applies to it. An office-first role reads five days a week; a sales role reads any major US city.

2026-09-11 — Every role is open, and applying takes about a minute

One hundred and twenty-nine jobs, each with its own page, its own description, and its own application. A reference number and an email the moment you apply. And the postings are visible to Google's jobs box, which until this release they were not.

All seventy-two catalog roles are open, and every one takes a real application

The role catalog had shipped as a map of intended work: seventy-two pages that each said there was no application to submit. Every role is open, every role now has a form on its own page, and the form is three fields. Fifty further roles that had full descriptions, requirements and success criteria, but existed only as rows inside one long page, now have pages of their own as well.

One hundred and twenty-nine jobs. One hundred and twenty-nine addresses.

A reference number, and an email that repeats what you sent

Applications used to arrive in the wrong inbox, and the applicant heard nothing back. Neither failure produced an error, which is why both lasted.

Every application now gets its own reference, and an email that reads back exactly what was stored rather than what the browser reported sending. Applying again to the same role with the same address updates the answers instead of creating a second record, and the reference stays the same. When the confirmation email does not send, the page says so and gives the address to write to, rather than pointing at an inbox nothing is coming to.

Show us everywhere your work lives

A resume, LinkedIn, a portfolio, GitHub, X, YouTube, Instagram, TikTok, Facebook, writing, Dribbble, Behance, and a box for anything else, whether that is a design workshop, a podcast, or a repository someone is proud of. Any of them, none of them. Only a name, an email and the role are required; everything else sits behind one link that opens on request.

The jobs box

Three faults were keeping almost every posting out of Google's jobs results, and not one of them ever produced an error message. A rejected posting simply never appears, which is indistinguishable from nobody searching for it.

The catalog roles carried no location, and location is required. The funded roles declared where a remote applicant could be based without the accompanying field that makes Google read it. And seven jobs shared a single address, competing against each other for one result.

Each job now has one page, one posting and one application. All of them are listed in the sitemap, and there is a feed for the job boards that ingest listings rather than crawling for them.

What this release deliberately does not do

It does not publish a salary it cannot stand behind. Attaching a pay band to a named job is a compensation decision, and those are made by people. Only the bands already published on the compensation page appear in the postings; the rest carry none rather than an estimate.

Verified in production

Every one of the seventy-two catalog roles and all fifty-seven of the new role pages were checked live after the release: each reachable, each carrying its own posting, each offering a working application. Addresses that do not exist return a proper not-found rather than an empty page pretending to be a job.

Sources