Quickstart

1. Install

npm i -g hypaware
hyp setup

Setup walks you through it: pick the tools to record, install the daemon, and attach the tools you picked. When it finishes it shows you what it has already found on the machine.

2. Check it is capturing

hyp status

This is the answer to "is HypAware working." It shows the daemon, what is being recorded, which tools are attached, the retention window, and anything that needs attention. Add --json for machine-readable output.

3. Look at what you already have

hyp query overview

Your history was already on the machine. This summarizes it: sessions, tools, models, and tokens over the last 30 days.

4. Ask it a question

hyp ask "From my HypAware history, which repo used the most tokens this month, and which model?"

To find out what repos are consuming the most tokens this month.

hyp ask "From my HypAware history, where did my agents go off the rails recently?"

To see where agents are spinning their wheels.

hyp ask "From my HypAware history, which tools failed most often this week?"

To find where the agents are having repeated tool failures.

5. Connect to your team

hyp remote login

Works whether you have an account or not. It opens a browser sign-in, enrolls this machine with your organization, and starts forwarding what it records. From then on you can query across every connected machine, not only your own:

hyp ask "From our HypAware team history, which of our sessions this week reached a pull request?"

To find out where your software factory is shipping.

One person can sign in and sync on their own. To add teammates to your organization, contact us at hypaware.ai/contact.

6. Control what is recorded

Mark any folder as ignore (never recorded), local-only (recorded, never synced), or sync, with a .hypignore file in the repo or with the hyp privacy commands. To be asked before each new folder is synced:

hyp privacy folders ask

To keep one conversation out of the record, hyp session ignore. To delete local recordings, hyp privacy purge. To stop syncing this machine, hyp leave.

7. Add or remove a tool

hyp attach <client>

Attaching is idempotent; run it again and nothing changes. hyp detach <client> removes only the settings HypAware added. Then hyp status to confirm.

Where to go next

The full reference, every command and every option, is in the docs. If something in this guide did not work the way it says, talk to an engineer; that is exactly the kind of thing we want to hear.