How MeowByte works

A short reference for the mechanics behind personalities, the Council, and usage.

Personalities

A personality is the unit you actually talk to. Each one has a name, a system prompt, a model, and generation parameters (temperature, top-p, max tokens). Create as many as you want - a blunt code reviewer and a patient explainer can both exist, backed by different models, without stepping on each other.

Every account starts with a few built-in personalities already configured, so there's something to talk to before you build your own.

Model routing

MeowByte doesn't call any model provider directly. Every completion goes through OpenRouter, which means a personality can point at effectively any model on the market and be repointed later without losing its system prompt, history, or conversations.

Which models are available to you depends on your tier - see pricing for the breakdown.

The Council

The Council seats two to six personalities around a topic and runs them through five structured phases:

The full transcript - every phase, every participant's contribution - stays attached to the council session, and you can pause, resume, or cancel a run in progress.

Usage and tiers

Every message a model generates - chat replies, personality previews while you're editing one, and each council participant's turn - debits the same weekly token quota. The quota resets automatically each Monday at 00:00 UTC; nothing rolls over and nothing expires early.

See pricing for the exact weekly quota and model access on each tier.

Accounts and usernames

Sign up with an email and password. Your handle follows the same pattern Discord made familiar - a display name plus a five-digit discriminator, like brad#12345 - so display names don't have to be globally unique.