How Kiwari remembers your game

If you work on more than one game, you know the failure mode: you re-explain your conventions every session, and context from one project leaks into another. Kiwari's answer is projects, each with its own chats and its own memory.

Each game keeps to itself

A project groups the chats for one game. Switch to a different place and you switch into that game's chats and that game's memory. The tycoon's DataStore scheme does not bleed into the obby, and a decision you made in March for one game does not quietly steer the other.

Memory you can actually see

Kiwari remembers two kinds of things:

• Project memory belongs to one game: how its systems fit together, what the save format looks like, which folder is legacy and off limits.
• Global memory follows you to every place: your naming conventions, how you like scripts organized, the way you want UI built.

None of it is hidden. Open the project's menu in the sidebar and choose Memory to see every note, per project and global. You can add notes yourself, edit them, and delete the ones that are stale. If Kiwari remembered something wrong, correct the note once and the corrected version is what it uses from then on. Memory lives in the app on your Mac; nothing is written into your place.

What is worth remembering

Memory works best for decisions and conventions, not day-to-day state. Good candidates:

• "DataStores save on a 60 second timer with session locking. Do not change the format without a migration."
• "One RemoteEvent per feature, named after the feature."
• "UI uses the dark theme. Do not introduce new colors."
• "The legacy folder is kept for reference. Never edit it."

A note like these turns every new chat into a continuation instead of a cold start. You stop re-explaining the project and get straight to the work.

It compounds over a project

The longer a project runs, the more this matters. Early chats set conventions. Later chats inherit them, and the notes you corrected along the way stay corrected. When you come back to a game after weeks away, the project still knows what you agreed, which is usually the moment other tools make you start over.

Related: How to get started with Kiwari · Review every change before it lands · Download