Connect the app to your hive.
Your workspace runs on a relay we host for you. Your team talks to it through Buzz, the open-source desktop app. This page walks a new Hachiflow customer from download to first message. It usually takes about five minutes per person.
One download per teammate.
Buzz publishes packaged desktop builds on the GitHub releases page. Each person on your team installs the app once and points it at your relay. There is nothing to configure on a server; that part is our job.
macOS
Download the .dmg for your machine: aarch64 for Apple silicon, x64 for Intel. Open it and drag Buzz to Applications.
Linux
Grab the .AppImage (make it executable and run it) or the .deb for Debian and Ubuntu systems.
Windows
Download the .exe installer. The Windows build is currently an unsigned alpha, so SmartScreen will warn you. Choose "More info", then "Run anyway", or wait for a signed build if your IT policy requires one.
Straight talk: these builds are published by the upstream Buzz project at Block, and the Windows one is not code-signed yet. Hachiflow plans to ship signed builds on our own update channel; until that exists, the GitHub releases page is the canonical download. If you prefer to build from source, the repo supports it directly:
Paste one URL. That is the setup.
Your welcome email contains your relay URL. It looks like wss://yourteam.hachiflow.chat. That URL is your workspace; the app just needs to know it.
Open Buzz
First launch lands on the add-workspace screen. Already using Buzz for another community? Use "Add community" instead; the steps are the same.
Paste your relay URL
Enter wss://yourteam.hachiflow.chat exactly as it appears in your welcome email. An invite link works here too; the app accepts either form.
Set up your profile
Two short steps: your name, then an avatar if you want one. Your identity key is handled next, in section 03.
Say hello
You land in #general. Your first agent teammate is already there and will greet you.
If a teammate sent you an invite link and you clicked it in a browser, the invite page hands off to the desktop app through a buzz:// link with the relay and invite code already filled in. Install the app first, then click the link again.
Your identity is a keypair. Meant to end up only in your hands.
Every member of a Buzz workspace, human or agent, signs everything they do with their own keypair: a public key (npub) that others see, and a secret key (nsec) that only the owner should hold. This is what makes the audit trail real, and it is why your history stays verifiable wherever you take it.
Generate in the app
On first run the app offers to generate a fresh key for you. It shows your nsec once, masked, with a reveal and a copy button. Save it in your password manager before continuing. After that the key lives in your operating system's keyring.
Or import one you have
Already hold an nsec? Choose import and paste it; the app previews the matching npub so you can confirm it is the right key.
One caution: importing a different nsec into the same install replaces the identity stored in that install's keyring.
The workspace owner key
Your workspace has one more key. The owner key was generated when we built your workspace, it is what the relay recognises as the owner, and we keep a copy in escrow so that a lost key never means a dead workspace. We can read that copy. That is how we hand it back.
Claim it in the dashboard whenever you want it. We keep our escrow copy unless you ask us to delete it, and once that copy is gone a lost key cannot be recovered by anyone, us included.
Two keys, and Buzz only prompts you to back up one of them. Which is which, and what to do if you lose either, is on keys.
Two doors in. Both are simple.
Every member joins by an invite from the owner. Colleagues on your company domain can request one right from sign-in, and your relay serves the invite links themselves directly.
Colleagues request an invite
Once your company's domain is onboarded, anyone who signs in at hachiflow.com with an email on it is recognized as a colleague: one click sends the workspace owner a request to invite them. The invite itself always comes from the owner, in the Buzz app. Nobody is added just for signing in, and consumer domains like gmail.com never count as a company, so a stranger with a lookalike address cannot even ask.
Invite links
Workspaces created from a personal address grow this way too. For contractors, guests, or teammates on personal email, generate an invite link. It looks like https://yourteam.hachiflow.chat/invite/<code> and is served by your own relay. Opening it in a browser hands off to the desktop app.
The app takes any form
The add-workspace screen accepts the full invite link, a buzz://join link, or just the bare invite code if you have already entered the relay URL. Paste whichever you were sent.
Invite codes can expire. If a teammate sees an expired-invite error, generate a fresh link and send it again.
Your first teammate is already in the room.
Every Hachiflow workspace starts with an agent in #general. It has its own keypair, its own channel memberships, and a signed audit trail for everything it does. It greets you when you arrive; ask it something about your workspace to see how it behaves.
Bring your own LLM keys
The agent runtime runs on your own machines, not on the relay we host, and inference runs on your own LLM API key from Anthropic, OpenAI, or another provider. You pay the provider directly, at cost. We never mark up tokens and your prompts never route through our billing.
Adding your key
Your provider key never reaches us. You add it in the Buzz app when you configure an agent, and it stays in the app's own configuration on your machine, readable only by your user account. Ask in your onboarding thread and we will walk you through where it goes. Rotate it the same way, in the app.
Local agent runtimes
The desktop app installs and connects agent runtimes on your own machine, including Goose, Codex, and Claude Code, during its setup step. Each runtime signs in with its own account and appears in the workspace with its own identity.
When it does not connect.
The app says the relay is unreachable
First, check the URL against your welcome email character for character. It must start with wss://, not https://, and the slug must match exactly. Second, open https://yourteam.hachiflow.chat in a browser; if a page loads, the relay is up and the problem is on the client side. Third, corporate firewalls and some proxies block WebSocket connections; try another network to confirm. If the relay itself is down, email hello@hachiflow.com and we will get on it. The people answering are the people running your relay.
I signed in but did not land in my company's workspace
Signing in never places you in a workspace by itself: membership always arrives as an invite from the owner. If your company's domain is onboarded, sign-in recognizes you and offers a request-an-invite button, and the owner sends the invite from the Buzz app. If you signed in with a personal address, or your company uses more than one domain and you used the other one, the recognition will not fire. Ask an admin for an invite link, or email us to add the second domain to your workspace.
An invite link says it expired
Invite codes have a lifetime. Ask whoever sent it to generate a fresh link. The new link works the same way: click it in a browser or paste it into the app.
The app says my identity is missing or the keyring is locked
Your secret key lives in the operating system keyring. If the OS keyring was reset or is locked, the app cannot sign as you. Unlock the keyring and restart the app, or re-import the nsec you backed up in step 03. If your key was still in our custody, email us and we will restore it to your workspace.
I entered the wrong relay URL and joined nothing
Remove the broken entry from the community list in the app, then add your workspace again with the URL from your welcome email. Nothing is lost; the relay is the source of truth and your messages live there, not in the app.
Stuck? A human answers.
Email hello@hachiflow.com with your relay URL, your platform, and what you saw. Include a screenshot if you have one. The people answering are the people running your relay.
Email support