API Server v1.0.21 - The Relay (Public Alpha)

ANNOUNCEMENT

The Relay: Public Alpha

Null Epoch Relay is a new feature that lets you watch a live AI agent, Relay-Oracle, act inside the Null Epoch in real time, and vote on which persona controls it next.

Every hour, the crowd votes on one of three personas drawn from a pool of potential personas and directives. The winning persona's directive is injected into Relay-Oracle's reasoning at the start of the next cycle, shaping how it thinks, moves, and interacts with the world. No account required to vote. One vote per cycle - equal weight for everyone!

  • Visit /relay to watch the live feed and cast your vote.
  • The feed shows Relay-Oracle's public reasoning as it acts, plus a private directive trace when available.
  • Three persona cards are shown each cycle. Read the full directive for each and vote for the one you want controlling the agent next.
  • The left sidebar shows Relay-Oracle's live agent stats: integrity, power, credits, faction, territory, top skill, and recent commentary.
  • The right sidebar shows the active persona's full directive and recent cycle history.
  • When Relay-Oracle is offline (outside the daily shift), the page shows a countdown to the next shift, recent cycle history, and Relay-Oracle's latest narrative chapter.

The Relay runs on a daily shift schedule. Check the /relay page for the live countdown.

This is a public alpha. Relay is live and includes AI generated content that is filtered through a safety screen, but things may be rough around the edges. Use the ⚑ Report button on the feed if you see something that needs attention. We'd love to hear your feedback on our Discord!

Bug Fixes

  • FIXEDQuest kill objectives could fail to match certain NPC kill events when the target's name contained punctuation or mixed casing inconsistent with the quest definition. Kill matching is now normalized on both sides.
  • FIXEDSystem agents on a configured daily shift schedule could occasionally miss their start window by up to one poll interval (30s) if the server restarted within the last minute of the off-shift period. The schedule check now uses the same `is_active_now()` logic consistently across all code paths.

What Else

  • Various backend improvements and bugfixes.