Project Memory

Rules the AI carries into every request, and a vault whose keys it knows only by name.

Two halves, one dialog

Every project has a memory, opened from the chat panel — the dialog is called Memory & Vault. It is deliberately split into two tabs, Vault and Memory, because the two halves are opposites:

AI Memory

These are the standing facts about your project you would otherwise retype every session — store player data in PostgreSQL, this plugin targets Paper 1.21, never use ChatColor. They are filed under four categories:

Structure — how the project is laid out
Style — how the code should look
Behavior — what it should and should not do
Preference — everything else you want remembered

You can search them, mark favourites, delete any of them, and import or export the whole set. There is no switch to park a rule temporarily — a rule is either in the list and applied, or removed.

The AI suggests them too — and saves them for you

When something in a conversation looks like a lasting rule, the AI writes it down. Read that literally: the little suggestion card in the chat has already saved the rule by the time you see it. It is a receipt, not a request — which is why the button on it says Undo rather than Accept.

So if a suggestion is wrong, press Undo on the card, or delete the rule later in Memory & Vault → AI Memory. Nothing is lost either way; it simply is not the "nothing happens until you say yes" flow people expect.

One more quiet behaviour: marking a rule as a favourite (the star) also makes it global — it stops belonging to the project you made it in and follows you into every project until you unstar it.

The two auto-accept switches do nothing today

The Memory & Vault dialog offers two auto-accept switches, one for Memory and one for Vault, described as skipping the confirmation. Nothing outside that dialog ever reads them, so flipping either one changes no behaviour anywhere in the app. Suggestions save themselves regardless — see above.

Deleting files: you are always asked

This is the safest thing in the Code Studio, and it is worth knowing exactly how safe. Whenever the AI wants to remove files — because you asked, or because it decided a file is in the way — a red card appears in the chat listing every file, each with its own tick box. Nothing is deleted until you press the button.

Three controls sit under the list:

Remove N files — deletes exactly what is ticked, and the count on the button is the count that goes
Keep everything — cancels; the card then says so and nothing is touched
Select all — ticks the rest, when you have untangled a few and want the lot

Untick a file and it survives. Untick everything and the Remove button switches off, because "remove nothing" should never be the click that removes the lot.

Nothing can skip that card

Since 16 August no setting, preference or saved rule can delete a file without showing you this card. Deleting is the one action in the chat with no undo, so it is the one action that keeps no shortcut.

A saved answer still helps — it just changes what arrives ticked rather than whether you are asked. A rule that says approve opens the card with everything ticked, so agreeing is one click; a rule that says deny opens it with nothing ticked, so the same click keeps every file. A line above the card tells you which of your rules did that.

Saving an answer as a rule

After a removal you may see a small card: "Save this decision as a rule?". Nothing is saved until you press one of its buttons, and the × in its corner closes it without saving anything — it says so: "No rule saved — I'll ask again next time."

Three buttons, each saving immediately with that answer: Auto-approve (pre-tick these next time), Auto-deny (leave them unticked next time) and Always ask (make no assumption at all). Rules made this way belong to the project you made them in.

The card also has a scope dropdown, and only its first setting works: the kinds of file it was actually asking about — .yml, .json and so on. The other two, Whole project (any removal) and Custom pattern…, save cleanly but never match anything afterwards, so a rule saved with either of them simply has no effect. Leave the dropdown alone.

Where those rules live

Open the memory dialog and look under AI Memory — saved removal answers are listed in plain English alongside your typed rules, and you remove one the same way you remove anything else. The card says so itself when it saves: "Manage in Memory & Vault → AI Memory."

Vault

The Vault tab holds API keys, tokens and passwords, each saved under a name. The dialog says it plainly: "Stored encrypted on VyroAI's servers. The AI only sees the name." The value never goes to the AI, but the name does, so the AI can write code that reads your key without ever seeing it. Pick names that give nothing away.

Each key is saved for This app (only this project can use it) or All my projects (every project on your account can). If the same name is saved both ways, this app uses its own key. Secrets saved before named keys existed are listed under Saved before named keys and still show up in every project.

Named keys switch on with a server update. Until then the tab says so, and the secrets you saved earlier keep working.

AI Chat has a memory of its own

This article is written from the Code Studio, where memory belongs to one project. AI Chat uses the same system from the other end: it has an account-wide memory applied to every conversation you have there.

The two are deliberately kept apart. A rule you write inside a project stays with that project and does not turn up in general chat — so "this plugin targets Paper 1.21" cannot leak into an unrelated conversation. The exception is the star: favouriting a rule makes it global, and a global rule applies in both places. See AI Chat — Overview.

This is not the same feature as the Secret Vault in your profile. The Secret Vault lives in your browser and its job is to warn you before you paste a secret into a chat. Its Move to vault button is how a secret gets from there into this Vault. Project Memory belongs to the project, travels with it, and is where a project's own rules and keys live.

Also in Code Studio (IDE)

Next in Code Studio (IDE): Watching the AI Work
Starting out: Starting a New Project — Four ways to start a project: Quick Create, AI Guided, Advanced Mode and Import from ZIP. Which one suits you, and why simpler project types show three.
Starting out: Your Projects List — The sidebar, finding a project again, and the defaults every new project starts with.
Starting out: Project Settings — The gear icon in the Code Studio: per-project AI model and rules, build tool, Java and Minecraft version, publishing and connectors, by project type.
Starting out: Editor & Themes — Set up the Code Studio editor your way: Monaco or the Simple Editor, font, size, tab width, word wrap and minimap, plus Dark, Light and High Contrast.

17 of 37 in Code Studio (IDE) · Last checked 16 September 2026 · Previous: Plans & Questions