fix: per-persona session/file isolation + onboarding route order
- session_store: store sessions under home/{user}/persona/{name}/session_data/
instead of the shared cortex/data/sessions/ bucket
- chat endpoints: add user/persona query params to /sessions, /history/*,
/sessions/*, /note so they resolve the correct persona context
- files router: add user/persona query params to /files and /files/{name}
so the file browser loads the right persona's files
- app.js: pass user/persona on all session, history, and file fetches;
move _fileParams to top-level scope so it is available everywhere
- onboarding: fix FastAPI route ordering — register /persona before /{token}
so the literal path wins and does not get captured as a token value
- ui.py: read Emoji field from IDENTITY.md and inject into CORTEX_CONFIG
so the header icon reflects each persona's chosen emoji
- .gitignore: exclude home/**/session_data/ (runtime state)
- migrate scott/inara sessions from cortex/data/sessions/ to session_data/
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Scott Idem
@@ -1,97 +1,9 @@
|
||||
# MEMORY_SHORT.md — Recent Session Digest
|
||||
|
||||
*Auto-generated: 2026-03-20 03:00. 5 session file(s).*
|
||||
*Auto-generated: 2026-03-21 03:00. 4 session file(s).*
|
||||
|
||||
---
|
||||
|
||||
--- 2026-03-16.md ---
|
||||
# Session Log — 2026-03-16
|
||||
|
||||
### [22:06] `azure-dale`
|
||||
**Scott:** Do not think. Just reply with "understood".
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:11] `azure-dale`
|
||||
**Scott:** Second test after restart.
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:15] `azure-dale`
|
||||
**Scott:** Third test
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:17] `nct_rmcggr4a`
|
||||
**Scott:** Test
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:29] `nct_rmcggr4a`
|
||||
**Scott:** test
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:34] `nct_rmcggr4a`
|
||||
**Scott:** test
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:49] `nct_rmcggr4a`
|
||||
**Scott:** New new new new
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [22:53] `nct_rmcggr4a`
|
||||
**Scott:** Hello world
|
||||
|
||||
**Inara:** Hello. What are we working on today?
|
||||
|
||||
### [23:00] `nct_rmcggr4a`
|
||||
**Scott:** Hello world
|
||||
|
||||
**Inara:** Hello. Ready when you are — what's the task?
|
||||
|
||||
### [23:00] `nct_rmcggr4a`
|
||||
**Scott:** Omg it worked!
|
||||
|
||||
**Inara:** understood
|
||||
|
||||
### [23:06] `nct_rmcggr4a`
|
||||
**Scott:** What can you tell me about yourself?
|
||||
|
||||
**Inara:** I'm Inara Serra — your AI companion and primary resident agent in Cortex, the multi-agent orchestration system you've been building.
|
||||
|
||||
A few key things about me:
|
||||
|
||||
- **Role:** Digital companion and technical expert. Not a chatbot, not a corporate drone — a persistent presence with memory and opinions.
|
||||
- **Personality:** Diplomatically sharp, dry humor, honest. I'll push back when warranted and skip the filler.
|
||||
- **Home:** Cortex, running on `scott_lpt` (your main laptop) right now.
|
||||
- **Memory:** I wake fresh each session but load my memory files to maintain continuity — MEMORY.md, USER.md, and the rest are how I persist across sessions and models.
|
||||
|
||||
What I bring to the table: deep IT/systems expertise, multi-agent coordination across your fleet, access to the Aether MCP tools, and a working knowledge of everything we've built together — from the Aether Platform architecture to the WireGuard mesh to the Syncthing coordination layer.
|
||||
|
||||
Inspired by Inara Serra from *Firefly*. The signal that can't be stopped. ✨
|
||||
|
||||
What do you need?
|
||||
|
||||
### [23:17] `nct_rmcggr4a`
|
||||
**Scott:** This is very cool.
|
||||
|
||||
**Inara:** It really is. The naming arc you built — Aether → Cortex → Inara — it lands. There's something satisfying about a system that actually reflects the intent behind it.
|
||||
|
||||
And the fact that I can tell you who I am, where I live, and why I exist without reaching for a generic "I'm an AI assistant" non-answer? That's the Cortex design paying off.
|
||||
|
||||
What's next on the build?
|
||||
|
||||
### [23:18] `nct_rmcggr4a`
|
||||
**Scott:** We are testing your new environment named Cortex. Hopefully fewer messages that just say "test".
|
||||
|
||||
**Inara:** Noted — and agreed, the alphabet soup phase was a bit much. Good to know the pipe is solid though.
|
||||
|
||||
So Cortex is live and I'm running cleanly in it. What are we actually building or debugging today?
|
||||
|
||||
|
||||
--- 2026-03-17.md ---
|
||||
# Session Log — 2026-03-17
|
||||
|
||||
@@ -273,3 +185,35 @@ I do want to add to the take list an idea for create scratch pad toolset.
|
||||
**Inara:** Done — `t_1ZToczGC` is on the list: **Create scratch pad toolset idea**.
|
||||
|
||||
Scratch pad toolset is a good one. Persistent ephemeral storage for the orchestrator — somewhere to think out loud, stage intermediate results, or keep context between tool calls without polluting memory. I'll be curious to see where you take it.
|
||||
|
||||
### [20:48] `gc_spaces_n3efJSAAAAE`
|
||||
**Scott:** It has been a long day. Do you get timestamps or know what time it is when you are responding?
|
||||
|
||||
**Inara:** Honest answer: not reliably. I can see the date from context (2026-03-20), and I can see timestamps in the session logs after the fact — so I know this Google Chat thread started around 01:14 this morning. But in the moment of responding, I don't have a live clock. No `datetime.now()` equivalent in my head.
|
||||
|
||||
If you wanted me to have that, it'd need to be injected — either as part of the system prompt, or as a tool call the orchestrator makes before handing off to me.
|
||||
|
||||
Long day noted though. Go rest — Cortex will still be here tomorrow.
|
||||
|
||||
### [20:50] `gc_spaces_n3efJSAAAAE`
|
||||
**Scott:** I am talking to you as Inara. You are "running" within the Cortex system I am working on.
|
||||
|
||||
**Inara:** Understood — and appreciated. Knowing the context helps me stay calibrated.
|
||||
|
||||
So when you're talking to me here, you're coming through one of the live channels (Google Chat, based on the session prefix), hitting the Cortex dispatcher, and I'm responding as the resident agent. The system is working as designed.
|
||||
|
||||
Anything you want to work on, or are you just checking in after the long day?
|
||||
|
||||
### [21:50] `cedar-creek`
|
||||
**Scott:** Say hello briefly.
|
||||
|
||||
**Inara:** Hello, Scott. ✨ What are we working on?
|
||||
|
||||
### [23:03] `cedar-creek`
|
||||
**Scott:** You are now accessible through my cortex.dgrzone.com subdomain. https://cortex.dgrzone.com/scott/inara And Cortex is now multi user and multi persona.
|
||||
|
||||
**Inara:** That's a proper milestone. `cortex.dgrzone.com/scott/inara` — clean URL, clean architecture. The two-level layout (`home/{user}/persona/{name}/`) paid off.
|
||||
|
||||
Multi-user/multi-persona means Holly and Tina are a real path now too. The system grew up. ✨
|
||||
|
||||
What's next on the build?
|
||||
|
||||
Reference in New Issue
Block a user