I build tools for people who work across multiple AI agents and want the results to remain useful after a session ends.
Your agents do valuable work. Actanara makes sure that work does not disappear with the session.
Actanara (formerly Open Nova) is a structured, local-first AI asset operations system. It consolidates sessions, tasks, and evidence from Codex, Claude Code, Gemini CLI, OpenClaw, Hermes, OpenCode, Antigravity, and Cursor into one durable local layer, then turns them into:
- shared memory across agents β work done in Claude Code can be found and reused from Codex through a restricted read-only retrieval boundary (
nova-RAGwith a local lexical fallback); - a graph of work that actually happened β
Nova-Taskderives tasks, status, and evidence from conversations, file changes, and tool results, not just manually written tickets; - automatic work narratives β daily, weekly, and monthly reports that turn fragmented sessions into durable progress;
- a local source of truth β sessions, usage, generated assets, and task evidence stay in user-controlled storage with explicit integration boundaries.
Parser-first processing normalizes everything before any LLM sees it; your runtime data and generated assets remain under your control.
Repository Β Β·Β Website
|
One living dial for your AI coding tools.
TokenClock reads local usage logs from Claude Code, Codex, Gemini CLI, OpenCode, and more, then turns them into an always-visible Liquid Glass view of tokens, messages, active tools, and per-session usage β broken down into sessions, models, and tools. Local-only Β· zero upload Β· native Liquid Glass on macOS 26+. Explore TokenClock β |
Switch between providers and models in Codex, Claude Code, and OpenCode β without editing config files or scattering API keys.
cdx glm52 # Codex with GLM 5.2
cld k3 # Claude Code with Kimi K3
opc ds # OpenCode with DeepSeekOne binary, three entry points (cdx / cld / opc). MuxLM is a lightweight switcher, not a proxy: the underlying CLI connects directly to your chosen provider, the launch config stays isolated from your global one, and nothing is left behind.
When I'm not building tools, I keep a small personal space at ailyre.com β a quiet homepage with an interactive lyre, an AI-news digest you can subscribe to, and room for curiosity to grow.
δΏζε₯½ε₯οΌθͺε¨ηιΏγ (Stay curious, grow at ease.)
- Local by default β private work should not need a cloud account to become useful.
- Interoperable by design β knowledge should move across tools without one agent owning the whole workflow.
- Durable outcomes β sessions should become evidence, memory, and reusable assets instead of disposable chat history.
- Explicit boundaries β automation is most valuable when its permissions, data paths, and failure modes stay visible.
My Gods are in the Rain.


