Private graphs are isolated per user; shared graphs are common to everyone.
| User | Role | Private memories | Graphs in use | Last login |
|---|
Readable and writable by every account.
| Graph | Memories | Entities | Facts |
|---|
Everything routed through the shared messages_to_send graph. Not loaded until you ask.
| From | To | Message | Sent | State |
|---|
Off for everyone until enabled here. Once a feature is on, each user chooses whether to use it.
Enable a card to show it in the chat sidebar. The Memory tab always lists every graph. Hidden from the sidebar by default.
Admins can read every user's graphs; normal users only see their own plus the shared ones.
| Username | Name | Contact | Role | Status |
|---|
A full set of private graphs is provisioned on first use. Email and phone number are both required.
Takes effect at once and signs nobody out. Juno never mails the new password, so hand it over yourself.
Both are required on every account. Accounts made before this rule show up blank in the table above and can be filled in here.
Juno normally learns only from conversations. Optionally drop plain text files here and it will derive standalone memories from them and file each one under the graph it belongs to. Official policies belong in Admin Knowledge — everyone can read that graph, only administrators can write it, and it outranks every other graph when answers disagree. Saying what the files are helps it read them correctly.
Memories derived from the most recent upload. Restatements of something already known update the existing entry instead of adding a second one.
Drop a .zip downloaded from the Memory tab. The graph is installed as-is — passages, entities, facts and embeddings — with no Gemini call. This replaces whatever is already in the destination graph. A .txt dump still works; that path rebuilds the index and takes longer.
Erases stored memories along with the entities, facts and embeddings derived from them. This cannot be undone and there is no backup.
Tools exposed here are merged into every agent's toolset.
Optional. Juno works fine without any.
One bot serves this instance. Create it in Telegram with @BotFather and paste the token it gives you.
Nothing to set up per person. Users message the bot and send /login username password using their web credentials; the bot deletes that message once it has read it.
Issue a code instead when you would rather not ask someone to type their password — they send it as /start CODE and it works once.
Each one reaches that user's own agent and own memory, in the same conversation they have in the browser. Pausing a chat turns it away and stops it signing back in.