We published two public tools: @consenger/companion-sdk and @consenger/vifu.

This is a small release, but it also changes how we describe the product.

While building the Vifu web app, we found that a companion can make short game sessions feel more connected. A game session can stay simple and self-contained, while the companion layer keeps enough context to understand what happened, what the player tried, and how the experience should continue next time.

That is the direction we want to develop from here.

Why this matters

The goal is not to make every game rebuild its own AI, memory, auth, backend, and runtime stack.

The goal is to let a game or interactive app add a companion through a clear interface:

• the app stays responsible for the playable experience
• the SDK reports safe session context and app-owned actions
• Vifu provides the companion layer, backend, runtime surfaces, and release path

This should make companion-enabled games easier to build, easier to ship, and more interesting to play.

Next

The next step is to keep making this product shape simpler for developers: better SDK docs, clearer runtime docs, and a release flow that makes browser games and apps easier to connect to Vifu.