Projects: your chats grouped by game
Every chat about a game joins that game's project on its own. Give the project a brief and rules every chat starts with, find its chats in one place, search only them, and continue where you stopped.
On this page
A project is one of your games. Every chat about that game belongs to its project, so you can find them together, search only them, and give all of them the same starting point: a brief (what the game is and where it is going) and rules (the conventions every chat follows).
Projects are private to your account, unless you invite teammates into one: see Team projects.
How chats join a project
You do not have to file anything. When RoGenie works in a published place in your linked Studio, the chat is linked to that place and joins the place's project. The first chat in a place creates the project, named after the place.
- A chat keeps the place it started in. If you later run it with a different place open, it stays in its first project and RoGenie tells you: This chat was about A; you're in B now. Start a new chat for B to keep the two histories apart.
- Unpublished places have no place id yet. RoGenie gives such a place its own project marker (an attribute on
ServerStorage.RoGenie) as part of the first change it makes there, so its chats can find their project. Reading or inspecting the place, or a step that fails, never adds it. When you publish the place, the project follows it. This is rolling out gradually and needs plugin 1.1.152 or newer. - A copy of a place file (for example one you saved and published as a second game) gets its own project, marked as a copy.
- An older chat that was never linked to a place joins a project the next time it runs with a published place open. You can also move any chat by hand.
The Projects section
Projects are listed in the library above your folders, most recently active first, with how many chats each has. A green dot means the place is open in your Studio right now. Click a project to open its page.
To make a project yourself, click + next to Projects, or choose Move to project › New project… in a chat's menu.
The project page
| Tab | What it shows |
|---|---|
| Chats | Every chat in the project, newest first. Click one to open it. |
| Brief & rules | The project's brief and rules, with how many characters they use. |
| Progress | What the project's runs built, what is still open and what a passing play test verified. See Progress. |
Use the ⋯ menu on the page to rename, archive or delete the project. Archived projects leave the Projects list; their chats stay where they are. To find one again, click archived projects under the list, open it and choose Unarchive (or Delete). Deleting a project never deletes its chats: they simply leave the project and are not put back in one automatically. The next new chat you start in that place begins a fresh project for it, without the old brief and rules.
Brief and rules
Write them on the Brief & rules tab and click Save brief & rules.
- Brief: what the game is, its core loop, who it is for, what is done and what comes next. Up to 8,000 characters; chats read the first 4,000.
- Rules: conventions every chat of the project follows, for example "use
--!strict", "remotes live inReplicatedStorage.Remotes", "no Toolbox models". Up to 4,000 characters; chats read the first 2,000.
Every chat of the project starts with them, next to your standing instructions and project notes. Like the rest of memory, they are taken when a chat starts: a change shows up in new chats, and in a running chat after its next summary.
RoGenie checks the brief and rules when you save them. Text that tries to give the assistant new instructions, contains hidden characters, or looks like a password or key is refused with the reason, and nothing is saved.
Rules or project notes? Project notes live inside the place file, so everyone who edits the place shares them. A project's brief and rules live in your RoGenie account and are yours alone.
Progress
The Progress tab is the project's record of what its runs did. When a run in one of the project's chats ends, RoGenie adds what that run did, read from the run itself with no AI call (plan steps keep the plan's own titles):
| Group | What lands there |
|---|---|
| Open | Plan steps a run worked on but did not finish, steps that failed, and the other unfinished steps of a plan a run was working through. |
| Built | Plan steps a run completed, and the instances and scripts a run changed (a read never counts). |
| Verified | Built items that a passing play test named in its own code after their last change. A play test passes when it runs without an error; a value it reports as false does not fail it. Change one again and it goes back to Built. |
| Removed | Instances and files a run deleted. |
Each item says as of run and the date of the run that last touched it, and has a link to that chat. Recent runs lists how each run ended: finished, stopped, stopped at the usage limit or failed (no error text is kept).
- Forget (×) takes one item out. A later run can add it again.
- Reset progress clears the whole record. Chats, the brief and the rules stay.
New chats start with it. Like the brief and rules, a summary of the progress (open items first, at most 25 items) is part of what a new chat in the project starts with, labelled with the date of its last run. RoGenie is told it can be out of date and checks the place before relying on it. A chat that is already running sees newer progress after its next summary.
Progress only knows what runs did. Work you do by hand in Studio, or in a chat outside the project, is not in it. If a run's record was lost while RoGenie restarted, the tab says The progress may miss 1 run with a link to that chat. A play test only verifies the instances its code names, for example workspace.Shop.Door or workspace:WaitForChild("Shop"); saved-test replays are kept in their own history.
Continue this project
Continue this project on the Chats tab starts a new chat in the project with a suggested first message that picks up where your last chat stopped. Edit it or press Enter. The new chat starts with fresh chat memory plus the brief and rules.
Move a chat
Open a chat's ⋯ menu (in the library or the chat's header) and choose Move to project:
- pick another project to move it there,
- New project… to make one for it,
- Remove from project to take it out. A chat you took out is not put back automatically.
Moving a chat does not change its folder. Moving a chat of a published place into a project that has no place yet links that project to the place, so the place's next chats join it too.
The chat's header shows a chip with its project; click it to open the project page.
Search a project
While the open chat is in a project, the library search (Ctrl+K) offers This project and All chats above the results. See Search every chat.
When RoGenie looks up your earlier work with Search My Other Chats, it searches the chats of the same place first.
Limits
- Up to 200 projects per account.
- Up to 30 project changes (create, rename, save the brief, move a chat, delete, forget a progress item, reset progress) per minute.
- Progress keeps the newest 300 items and the last 30 runs of each project.
If projects are briefly unavailable, the library hides the section and your chats keep working as usual.
Privacy
Your projects, their brief and rules, and which chats belong to them are stored in your RoGenie account and are never shown to anyone else, unless you invite teammates into a project (what a team project shares). RoGenie links chats using what your own Studio reports about the open place; it fetches nothing from Roblox. A project's progress holds only the plan step titles (key-shaped secrets, such as API keys, are blanked), the instance and script paths and the play test names of your own runs; it goes when you delete the chat it came from, reset it, delete the project or delete your account, and it never passes to a team project's next owner. Deleting your account deletes your projects, except that a team project you own passes to its longest-standing editor without its progress (one with no editor is dissolved). See Privacy and your data.