“Horror stream next Friday. No backing out.”
The stream ends.
The lore doesn’t.
Keep your promises, give your mods the context, and bring new viewers into the story.
Shared memory for your Twitch community.

Confirmed promise
One spooky stream. Zero forgotten plans.
Chat moves on.
The good stuff stays.
The island tour you promised. The reason behind a mod’s call. That one joke nobody explains to newcomers.
Lore gives each a place to go, with the source attached and your team in control.
“Next stream”
has a place now.
Save a promise from your dashboard or with !promise in chat. Review optional chat or microphone suggestions before confirming them. Your next-stream brief brings open commitments and recent community updates together.
Example · Next-stream brief
Finish the community island tour
Cozybyte · Next stream
Source: “We’ll check out everyone’s gardens next time.”A handoff.
Not a guessing game.
Keep rules, evidence and earlier decisions in one private case file. Leave the next mod a clear handoff, with follow-ups they can act on.
Look inside a caseExample · Private moderator handoff
Spoiler appeal needs a second look
Read the saved incident note and rule version before making the call.
People decide. Lore keeps the context.
You don’t have to have been there.
Find a channel through Discover, read its catch-up and ask the community guide about a stream or an inside reference. Answers link to the published stories behind them. No account needed.
“First stream here. What’s with the garden?”Every new viewer starts somewhere.
Example · Public community guide
So, what’s with the garden?
Chat built an island garden together. We’re naming the pond next — bring your worst puns.
Source: The community garden is openBring the context back on stream.
Choose an approved recap or public plans for your OBS overlay. Let !catchup share the reviewed short version in Twitch chat. Update the story once, then share it where your viewers are.
Public stories can also carry a Twitch clip and a screenshot, so the moment has something to point to.
Preview the stream overlayA place for the whole crew.
Your private work stays private.
Case files and team notes stay in your private team area. Public stories are separate records that an owner or moderator reviews before publishing. Team AI tools require owner opt-in and human review. The public guide uses only published story text; owners can turn it off.
How access worksA few good questions.
Do I need a Twitch account?
Streamers and team members sign in with Twitch. Viewers can read published community pages without signing in. You can also try the demo without an account.
Will Lore moderate my chat for me?
No. Lore helps your team review cases and remember decisions. It doesn’t warn, time out, ban or unban anyone on Twitch.
What happens when I try the demo?
You get a sample community with promises, cases and public stories to explore. Changes stay in your browser session and reset on refresh. Chat, AI and OBS actions are simulations; the optional sample clip loads real Twitch playback.
Can I try it without configuring AI?
Yes. You can capture promises, review cases, manage handoffs and publish stories yourself. Gemini suggestions are optional, and every suggestion needs human review. The live public Q&A guide needs a configured Gemini connection.
Can the community guide read private chat or cases?
No. It answers from that channel’s approved public stories and links to its sources. If the published material does not cover your question, it should say so. Check the linked story before treating an AI answer as a fact.
Can I search for any Twitch channel?
Discover searches connected communities that have published on Lore. It does not search every Twitch channel or reveal private, unpublished workspaces.
Good memory, chat?
Flip two cards and find the matching pairs. Missed one? Turn another card and keep going.
Eight cards. Four pairs. Take your time.
Give the next “remember when?”
somewhere to live.
A sample community. No sign-in needed.