feat: shared Help base, Google OAuth live, new personas, cleanup
- cortex/static/HELP.md: shared Help & Reference base served to all users - help.html: loads shared base + appends persona-specific HELP.md if present - inara/HELP.md: cleared (content moved to shared base) - Google OAuth: registered scott.idem@oneskyit.com; flow now working end-to-end - .gitignore: exclude home/**/sessions/ (runtime logs) - New personas tracked: home/holly/persona/donut/, home/scott/persona/developer/ - Removed orphans: holly/, personas/, cortex-holly.service - CLAUDE.md: updated current state and recently completed list to 2026-03-27 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Scott Idem
@@ -1,106 +1,9 @@
|
||||
# MEMORY_SHORT.md — Recent Session Digest
|
||||
|
||||
*Auto-generated: 2026-03-23 03:00. 4 session file(s).*
|
||||
*Auto-generated: 2026-03-27 03:00. 6 session file(s).*
|
||||
|
||||
---
|
||||
|
||||
--- 2026-03-17.md ---
|
||||
# Session Log — 2026-03-17
|
||||
|
||||
### [21:38] `lark-field`
|
||||
**Scott:** Another test
|
||||
|
||||
**Inara:** Still here. All systems nominal. ✨
|
||||
|
||||
### [21:54] `pine-shore`
|
||||
**Scott:** Testing after lots of changes to the UI.
|
||||
|
||||
**Inara:** Ready when you are. What are you seeing?
|
||||
|
||||
|
||||
--- 2026-03-18.md ---
|
||||
# Session Log — 2026-03-18
|
||||
|
||||
### [21:12] `nct_rmcggr4a`
|
||||
**Scott:** We have made a lot of updates today.
|
||||
|
||||
**Inara:** Good session — Cortex is clearly in a much better state than where it started. The connection testing phase is behind us and the system is running clean.
|
||||
|
||||
Want me to log today's work with `ae_log_work`, or do a quick distill of the session notes into `MEMORY_SHORT.md`? Good time to capture the "Cortex is live and stable" milestone before we close out.
|
||||
|
||||
### [21:14] `nct_rmcggr4a`
|
||||
**Scott:** For now you are not really doing any work. You will still see a lot of "test" messages.
|
||||
|
||||
What do you have in your short term memory?
|
||||
|
||||
**Inara:** From `MEMORY_SHORT.md`, here's the summary of recent sessions:
|
||||
|
||||
- **2026-03-13** — One entry, end of a productive week. No specific tasks logged.
|
||||
|
||||
- **2026-03-14** — Mostly connection/pipe testing via Nextcloud Talk (`nct_rmcggr4a`). Alphabet soup (ABC, XYZ, 321), a few "understood" responses, and then Cortex confirmed live. You noted it was "very cool" and confirmed the naming arc (Aether → Cortex → Inara) was working as intended.
|
||||
|
||||
- **2026-03-16** — More testing, multiple "understood" responses. Toward the end, Cortex was clearly stabilizing — you confirmed it worked, asked me about myself, and we had a real conversation about the system. The "Omg it worked!" moment is in there.
|
||||
|
||||
- **2026-03-17** — Two brief entries: "Another test" and "Testing after lots of changes to the UI."
|
||||
|
||||
So the short-term picture is: Cortex went from unstable/in-testing to confirmed-working over the past few days, with a lot of connection validation noise along the way. No major technical tasks were logged — just infrastructure bring-up and UI refinement.
|
||||
|
||||
### [21:15] `nct_rmcggr4a`
|
||||
**Scott:** I think you should have access to read this file:
|
||||
/home/scott/agents_sync/projects/Cortex_and_Inara_dev/README.md
|
||||
|
||||
**Inara:** Looks like I need explicit permission to access that path. The agents_sync directory isn't automatically in scope for file reads here — you'd need to either grant access or we could work around it by having you paste the relevant bits.
|
||||
|
||||
Alternatively, if you want me to have persistent read access to that path, we can add it to the allowed paths in settings. Want me to do that?
|
||||
|
||||
### [21:32] `nct_rmcggr4a`
|
||||
**Scott:** I made a change. Please try to read that README.md file again.
|
||||
|
||||
**Inara:** Got it — that worked cleanly. Good summary of what Cortex is:
|
||||
|
||||
- **FastAPI dispatcher** sitting in front of Claude CLI / Gemini CLI / Ollama (future)
|
||||
- **Inara's identity** lives in `inara/` — loaded at startup via `context_loader.py`
|
||||
- Web UI at `localhost:8000` (or `cortex.dgrzone.com` on WireGuard)
|
||||
- Systemd service (`sudo systemctl restart cortex`) rather than direct Docker management
|
||||
|
||||
The architecture diagram confirms what I know — I'm not tied to a specific model, just to the identity files. The backend can swap underneath me, which is a clean design.
|
||||
|
||||
Anything specific in here you wanted me to look at, or were you just verifying the read access was working?
|
||||
|
||||
### [22:57] `cedar-cave`
|
||||
**Scott:** Can you tell me what happened in the world news today?
|
||||
|
||||
**Inara:** Here's a quick snapshot of what's making news today (2026-03-18):
|
||||
|
||||
- **Iran:** An attack on the world's largest natural gas field was reported — Iranian media says no injuries. Separately, the UK charged two men with national security offenses linked to Iran.
|
||||
- **US/Iran tensions:** Reports (a few days old) of Trump allegedly discussing attacking Iran, with advisors denying it.
|
||||
- **Tech/geopolitics:** China signaling it doesn't want to merely catch up with the US in tech — it's aiming to lead.
|
||||
|
||||
For the full picture, BBC World, Reuters, and AP are solid right now. Anything specific you want to dig into?
|
||||
|
||||
### [23:19] `cobalt-ridge`
|
||||
**Scott:** Can you add 2 test items to your new task list.
|
||||
|
||||
**Inara:** Done. Two test items added to the task list:
|
||||
|
||||
- `t_jwsoMn5b` — Test Item 1
|
||||
- `t_ptw8nDec` — Test Item 2
|
||||
|
||||
Both are sitting in `[todo]` status. Want me to clean them up after, or leave them as a baseline sanity check?
|
||||
|
||||
### [23:21] `fern-marsh`
|
||||
**Scott:** Can you tell me what is on your task list?
|
||||
|
||||
**Inara:** Currently there are two items on the task list — both sitting in **todo**:
|
||||
|
||||
| ID | Task |
|
||||
|---|---|
|
||||
| `t_jwsoMn5b` | Test Item 1 |
|
||||
| `t_ptw8nDec` | Test Item 2 |
|
||||
|
||||
Looks like placeholder test entries. Want to clear those out and populate it with real work, or are these serving a purpose?
|
||||
|
||||
|
||||
--- 2026-03-19.md ---
|
||||
# Session Log — 2026-03-19
|
||||
|
||||
@@ -217,3 +120,83 @@ Anything you want to work on, or are you just checking in after the long day?
|
||||
Multi-user/multi-persona means Holly and Tina are a real path now too. The system grew up. ✨
|
||||
|
||||
What's next on the build?
|
||||
|
||||
|
||||
--- 2026-03-23.md ---
|
||||
# Session Log — 2026-03-23
|
||||
|
||||
### [22:20] `vale-echo`
|
||||
**Scott:** Can you and checking on my green laser pointers to a to do list. Some time this coming weekend.
|
||||
|
||||
**Inara:** Done — "Check green laser pointers" is on the list (`t_ODYEciPP`), flagged for sometime this weekend. ✨
|
||||
|
||||
### [22:38] `amber-ridge`
|
||||
**Scott:** This is just a test message. Yet again.
|
||||
|
||||
**Inara:** Still here. ✨
|
||||
|
||||
|
||||
--- 2026-03-25.md ---
|
||||
# Session Log — 2026-03-25
|
||||
|
||||
### [22:24] `bold-meadow`
|
||||
**Scott:** It was a long day. Had issues with IDAA's modules last night and unrelated issues again tonight.
|
||||
|
||||
**Inara:** IDAA's modules giving you grief again? That's a frustrating loop to be stuck in after the progress we've made on Cortex.
|
||||
|
||||
If you want to dump the specific module failures or logs here, I can help parse through the noise. Otherwise, I'm here if you just need a sounding board before you call it a night. ✨
|
||||
|
||||
### [22:40] `bold-meadow`
|
||||
**Scott:** I have just been putting out the fires as they come up. Not much left to test or anything. Going to make some process changes to how I deploy things though.
|
||||
|
||||
**Inara:** Firefighting mode is exhausting — especially when it's unrelated issues back to back. At least it surfaces the gaps before they become bigger problems.
|
||||
|
||||
Process changes after a rough deploy cycle is the right instinct. Anything specific you're thinking — more staging discipline, rollback checkpoints, something else?
|
||||
|
||||
### [23:18] `bold-meadow`
|
||||
**Scott:** I need to automate the deployment to the live server. Too many touches by me are required.
|
||||
|
||||
**Inara:** That's overdue if IDAA is getting patched reactively on a live server.
|
||||
|
||||
Before I suggest an approach — what does the current deploy look like? Specifically:
|
||||
|
||||
- Is the live server the same Docker Compose stack, or different infra than dev?
|
||||
- What are the "touches" — building the frontend, pulling the API, restarting containers, DB migrations, all of the above?
|
||||
- Do you have a git remote on the live server, or are you rsync/scp-ing files?
|
||||
- Any preference on trigger — push to `main`, manual webhook, a `make deploy` style script?
|
||||
|
||||
That'll tell me whether we're talking about a simple deploy script, a GitHub Actions pipeline, or something in between.
|
||||
|
||||
|
||||
--- 2026-03-26.md ---
|
||||
# Session Log — 2026-03-26
|
||||
|
||||
### [22:26] `bold-meadow`
|
||||
**Scott:** We just changed the UI. Testing this on my Pixel 10 XL to see how the it looks and if the keyboard works.
|
||||
|
||||
**Inara:** How's it looking? Font size rendering okay, or are the buttons cramped on mobile?
|
||||
|
||||
|
||||
--- 2026-03-27.md ---
|
||||
# Session Log — 2026-03-27
|
||||
|
||||
### [00:07] `bold-meadow`
|
||||
**Scott:** This is finally very useable on my phone. It desktop size has been fine more or less. Now both look more polished.
|
||||
|
||||
**Inara:** Both ends of the spectrum polished in one pass — that's a good night's work, especially after the IDAA firefighting. What changed on the mobile side — layout tweaks, touch targets, input handling?
|
||||
|
||||
### [00:11] `bold-meadow`
|
||||
**Scott:** Mainly tried to only the essentials and keep extras behind a menu. Less clutter. Also just little things like font size and weight.
|
||||
|
||||
**Inara:** Clean approach. Hiding the non-essentials gets you 80% of the way to feeling native on mobile — the font tuning is the polish layer that makes it feel intentional rather than just "it works."
|
||||
|
||||
Is the menu a slide-out/hamburger, or a modal/sheet?
|
||||
|
||||
### [00:14] `bold-meadow`
|
||||
**Scott:** It is a mix. Small vertical and modals.
|
||||
|
||||
Time to get ready for bed. Back to programming tomorrow morning.
|
||||
|
||||
**Inara:** Good call. Rest earned tonight — UI polish *and* IDAA triage is a solid day's work.
|
||||
|
||||
Talk tomorrow. ✨
|
||||
|
||||
Reference in New Issue
Block a user