97438f1a0fc6516595abec309ce84f0273936216
All hardcoded "Inara"/"Scott" strings replaced with settings.agent_name and settings.user_name, read from .env at startup: - config.py: AGENT_NAME and USER_NAME settings (defaults: Inara / Scott) - llm_client.py: conversation labels in prompt builder - session_logger.py: **Name:** labels in session log markdown - memory_distiller.py: distillation system prompts (mid + long) - routers/nextcloud_talk.py: @mention prefix strip - routers/google_chat.py: greeting message Second instance scaffolding: - holly/: identity directory with placeholder files (USER_NAME=Holly, AGENT_NAME to be chosen by Holly) - cortex/.env.holly: config for Holly's instance on port 8001 - cortex-holly.service: systemd unit for the second instance No behavioural change to the Inara/Scott instance — defaults unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Cortex / Inara — Project Root
Owner: Scott Idem (One Sky IT / Danger Zone) Started: 2026-03-04 Status: Active development
"You can't stop the signal."
Cortex is a self-hosted multi-agent orchestration layer. Inara is the primary conversational agent that lives inside it.
Quick Orientation
| Directory | What it is |
|---|---|
cortex/ |
FastAPI service — dispatcher, routing, LLM backends, session management |
inara/ |
Inara identity, memory, context, and help files |
docs/ |
Integration reference docs (NC Talk bot, etc.) |
documentation/ |
Architecture decisions, project plans, agent task lists |
Running Cortex
# Start (Docker)
cd ~/agents_sync/projects/Cortex_and_Inara_dev
docker compose up -d
# Restart service only (after backend changes)
sudo systemctl restart cortex
# Logs
journalctl -u cortex -f
# Web UI
http://localhost:8000 (or cortex.dgrzone.com on WireGuard)
Config lives in cortex/config.py and a .env file at the project root (not tracked — see env.default).
Key Documentation
| File | Purpose |
|---|---|
documentation/TODO__Agents.md |
Active task list — read first |
documentation/ARCH__Intelligence_Layer.md |
Intelligence layer architecture (orchestrator, dev agents, knowledge) |
docs/NEXTCLOUD_TALK_BOT.md |
NC Talk bot setup |
inara/IDENTITY.md |
Inara persona and identity |
inara/HELP.md |
In-app help content (rendered in UI) |
inara/PROTOCOLS.md |
Inara behavioral protocols |
~/agents_sync/projects/CORTEX.md |
High-level project vision and phases |
Architecture at a Glance
[User / Cron / Webhook]
↓
Cortex Dispatcher (FastAPI, cortex/)
↓
LLM Backend(s)
• Claude CLI — primary reasoning, coding, long-context
• Gemini CLI — secondary / cost routing
• Ollama — offline/private (scott_gaming, future)
↓
Inara (identity + memory in inara/)
See documentation/ARCH__Intelligence_Layer.md for the evolving orchestrator/responder and dev-agent architecture.
Inara
Inara is not tied to a specific model. The name is fixed; the backend may vary.
Her identity and behavioral files live in inara/ and are loaded at startup via cortex/context_loader.py.
Related Projects
| Project | Path |
|---|---|
| Aether Platform API | ~/OSIT_dev/aether_api_fastapi/ |
| Aether Frontend | ~/OSIT_dev/aether_app_sveltekit/ |
| Fleet coordination | ~/agents_sync/ |
Description
Languages
Python
69.1%
HTML
14.1%
JavaScript
10.2%
CSS
6.2%
Shell
0.3%