Memory and knowledge

What it remembers about you#

Xertron keeps a short personal note about you, per server, and reads it alongside your messages. You write to it by asking, in the middle of an ordinary conversation. There is no command for saving a memory, on purpose.

• Remember that I prefer short, direct answers.
• What do you know about me?
• Forget everything you know about me.

What it knows about you is yours. Other members cannot see it, and it does not follow you to another server.

Run /memory at any time to see exactly what is stored about you in that server. It is a read-only view, shown only to you. To change anything, ask in the conversation as above, so there stays exactly one way a memory gets written.

Server memory#

Server memory is shared. It holds facts that apply to everyone, and anyone in the server can add to it or read from it the same conversational way.

• Add to server memory: our weekly meeting is every Friday at 3pm.
• What is in the server memory entry called meeting?
• Delete the server memory entry called old-topic.

When it is full, the oldest entry is dropped to make room for a new one. Nothing warns you first, so a server that leans on memory is worth tidying occasionally from the dashboard.

Xertron carries only the entry names with it by default and fetches the full text of one when it turns out to matter. That keeps 25 entries from crowding out the actual conversation.

The channel guide#

The channel guide is a short admin-written list of what each channel is for: which one is the FAQ, which one is patch notes, where support questions belong. Xertron reads it in every reply, on every plan, and uses it to point people at the right place.

It is edited on the dashboard, under Bot Knowledge. There is no Discord command for it, and it does not update itself, so it is worth revisiting whenever your channel structure changes much.

Reference files#

An artifact is a reference file an admin uploads for Xertron to know about: server rules, an onboarding document, a price sheet, a screenshot of a config. It is different from a file someone attaches in chat. An artifact never expires, and it applies everywhere in the server rather than in one channel.

There is nothing for a member to invoke. When you ask something an uploaded file would answer, Xertron searches its artifacts by meaning and works the result into its reply. If it says it has no artifact for something, either none has been uploaded or an admin needs to add one.

Uploading them

Admins upload on the dashboard's Bot Knowledge screen. Uploading needs Premium, though a server that drops to free keeps the files it already has, still uses them in replies, and can still remove them.

An upload is not staged like the other edits on that screen. The file is sent immediately so its text can be extracted and the upload confirmed as valid, which is why it processes for a few seconds before it appears. A freshly added file can take another moment to become searchable.

Reviewing it all#

The dashboard's Bot Knowledge screen holds all three in one place: the channel guide, the uploaded files, and the server's memories newest first with a meter showing how many of the 25 slots are used. When the store is full, the entry next to be dropped is flagged.

The memory section only lets an admin read and remove. There is deliberately no way to add or edit an entry there, because a memory is created by asking Xertron in Discord and that stays the single write path.

Nothing on the screen saves as you type. Edits across all three sections stage into a draft and one bar at the bottom saves or discards the lot. Saving the channel guide or a file description runs a safety review, so it takes a moment.

For what a member can reach and what an admin controls, see Plans.