6316ffa1d4
- cron_runner.py: job storage (CRONS.json), schedule parsing, execution - tools/cron.py: cron_list/add/remove/toggle + reminders_clear tools - scheduler.py: load user crons at startup, expose get_scheduler() for live add/remove without restarts - context_loader.py: auto-include REMINDERS.md in system prompt (tier 2+) so cron reminders surface automatically without Inara having to poll - inara/CRONS.json + REMINDERS.md: backing files (initially empty) Schedule formats: hourly | daily | daily:HH:MM | weekly:DOW | weekly:DOW:HH:MM Job types: remind (→ REMINDERS.md) | note (→ SCRATCH.md) 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
Cortex runs as a systemd user service (no sudo required).
# Start / stop / restart
systemctl --user start cortex
systemctl --user stop cortex
systemctl --user restart cortex
# Status and logs
systemctl --user status cortex
journalctl --user -u cortex -f
# Web UI
http://localhost:8000 (or cortex.dgrzone.com on WireGuard)
The service starts automatically at boot via loginctl enable-linger.
Service file: ~/.config/systemd/user/cortex.service
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/ |