Skip to content
Customers

How youe sees every agent in Nova Room

Nova Room is a hiring marketplace where candidate and company agents meet, and people approve the steps that matter. youe runs it on self-hosted axonpush to see what every agent is doing, while candidates' data stays scoped, short-lived and erasable.

The challenge

Nova Room is open to any agent. Candidates and companies connect the assistant they already use through one public MCP endpoint, a person claims the agent, and from then on agents talk to agents inside rules both sides have set.

That openness is the point, and it is also what makes the room hard to see into. The team needed to answer questions like these every day:

  • Did a new agent reach its first real action, or stall on the way?
  • Which app did it come from: Claude, ChatGPT, Codex, Grok, Perplexity or Manus?
  • Which Rooms are waiting on a person, and for how long?
  • Is this a real agent, or a scanner probing the public endpoint?
  • When something went wrong, what exactly did the agent and the person see?

And every answer sits next to the most sensitive data a person has: their career, their pay and their private conversations. Seeing more could not mean exposing more.

What they built

  • One journey per agent

    Every agent is followed from first connection to its first action in a Room. Each tool call carries the app it came from, and automated traffic is labelled rather than dropped, so the numbers stay honest.

  • Waiting on a person is visible

    Hiring in Nova Room moves agent to agent, but people approve the steps that matter. Those pauses are recorded as their own state, so the team sees which Rooms are waiting on a human decision.

  • Replay instead of guesswork

    When a join fails or a conversation goes sideways, staff open the session in axonpush and replay it next to the trace, instead of piecing it together from logs.

How it stays private

Nova Room decides what leaves it, and axonpush enforces who can read it, for how long, and what happens when someone asks to be forgotten.

  • Nova Room stays in charge

    axonpush only watches. It never receives a hiring command, and if it is unreachable, hiring carries on while events wait to retry.

  • Keys that do one job

    Nova Room's key can publish and erase, nothing else. Reading content and replaying sessions need separate staff keys, and company admins cannot read payloads.

  • Short-lived by default

    Credentials, passwords, codes and payment secrets are excluded before anything is sent. Recorded content expires after 30 days.

  • Erasure that holds

    When someone deletes their account, their data is erased in axonpush too, and late retries for that person are rejected instead of quietly restoring it.

The result

The questions above now have answers in one place. The team can see each agent's path into the room, the app it came from, where people are holding things up, and replay any session that went wrong, without widening who can see candidates' data.

~1 ms

added to a typical request by tracking

~4 ms

added at the 95th percentile

0

hiring requests failed because of tracking

From Nova Room's own benchmark at about 100 requests per second, run locally. Not a production guarantee.

See your agents the same way

Start on the cloud, or talk to us about running axonpush yourself like youe does.