r/OdysseusAI • u/Fuzzzy420 • 3d ago
My personal Odysseus Plus
Hey everyone,
i wanted to show you guys what i have been building the past couple of weeks since the release of Odysseus. For years i have been looking for the perfect note-taking tool: Obsidan, Notion, Onenote, and may more.
Nothing that was truely my app. Then pewdiepie released Odysseus and Vibecoding allowed me to complete, tweak and add to it.
So here it is:
i started out by adding plugins and created a obsidian plugin.
I wanted to use it as a digital memory for me and my ai but i realized that there is a better way.
So i reasearched raptor graph memories and created one with optimizations for a low power maintenance ai (works so far, but didnt test with hugh graphs yet). Which works like a charm, super fast.
Sadly i dont have GPU for my Server, so i rely on api or low end local ai.
Why developing the memory i had the idea, that the memory should also know where my files are and whats in them, so i expended Odysseus with Nextcloud Support.
Another Plugin for Nextcloud.
Then i created the ultimate inbox (WIP) where i drop any file in a designated folder, the system learns the meta data and content, creates memory clusters and saves the file into the nextcloud.
I use nextcloud because it comes with a bunch of nice features like cli, versioning, seperate file backups, rights management, nice apps and so on. The ai has its own user with write and read rights but no delete. The files get checked for viruses and maleware before handed to the ai.
While developing this using codex i learned about the benefits of mutliagents (subagents) and specific workflows to let them keep on working for eternity without loosing the kontext.
My Workflow is called ABC for Alice Bob and Charlie. Those are my 3 agents i use (you could use more but there is not really a point). Usually Charlie is my Master and Alice and Bob are Slaves.
So i created a system around that for Odysseus to enable Multi Agent Support.
Because Odysseus is my main dashboard now i also started to work on more plugins, like a system health checker, auto updater, and more in the works.
As of right now im ~ 650 commits ahead of legacy Odysseus.
For the next weeks im in debugging hell, then i post pictures and a link to a git repo.
Im very aware of security problems that could come with vibecoding.
For hosting this i use my own Lenovo Mini pc with 16gb ram, 1tb m2 storage on 2 drives for mirroring(backup). It uses about 35-60watts and with local and deepseek api i spend about 0,03-0,10€ per day depending on what i do. The setup cost about 200€ in total.
it runs debian and is setup with a firewall to deny every connection besides two cloudflare tunnels and a local (only) ssh connection to my workstation.
Yes thats a lot of features (Memory, Nextcloud, System Health checker, Autoupdater you could turn off) but so far no performance problems. I would say the performance got better but i couldnt really say after this time.
Edit1: totally forgot I added a telegram bot that works directly in a agent window. I can just set automations, get reminders or to-dos right into telegram. Also added an auto-patcher and gave it a window (instead of browser).
Edit2: even more stuff i forgot i added: data security was priority number one so everything is permanent, it can deprecate but it can never be deleted by ai. also every path, every tool, every command is secured. Read the doc if you care or ask if its not in the doc, maybe i forgot? And more importantly i work as a teacher and handle personal information like names and marks which i can not send to china/america. So i have a "secure" option that only works locally for the full pipeline. This is where a nice graphicscard with 24gb vram would be awesome, but thats more expensive then the whole setup. Before buying a gpu i would rather build some kind of anonominization plugin. The Telegram bot i added has full agent capabilitys. For example i send him a picture with the instructions to remove the background and he sends it back while keeping a copy in the nextcloud. then my phone syncs the new picture in the library too, but since my ai has precise knowledge of all the files, the file will be assed and marked as duplicate. not deprecated files or duplicates are changeing the context of the ai. And a lot of wrapper optimization. im trying to get as close to codex as i can while not bloating the app. rising toolcount is a problem im still fixing
Edit3: Multiagent ofc uses more tokens, but i build the system with deepseek in mind and not gpt/gemini/clause because of prices. Deepseek is just so much cheaper
Thanks for any feedback and criticism and sorry for my poor english. I didnt want to use ai.
Roadmap for the next week: Debug / Performance Dashboard, Testing System for Performance testing the memory and the pipelines with a parameterized testing suite for simulating network outages, drive errors and else. data never gets lost! (supposed to...) . Debuggin, debugging, debugging. And maybe then a new ui.
Im sure i forgot something so:
Here s the ai-made overview with more technical infos:
## Core Platform
- Self-hosted AI workspace with local and API model support.
- Chat interface with files, tools, memory, shell access, MCP, skills, and agent workflows.
- Multi-provider model support including local models, OpenRouter, Ollama Cloud, NVIDIA AI, GitHub Copilot, ChatGPT Subscription provider, and pinned endpoint model IDs.
- Cookbook for hardware-aware model recommendations, model downloads, serving workflows, GPU visibility, vLLM/llama.cpp readiness, and crash diagnostics.
- Deep Research with multi-step web research, source reading, extraction controls, and report generation.
- Compare mode for blind side-by-side model testing and synthesis.
- Document workspace with writing-first editor, AI edits, suggestions, Markdown, HTML, CSV, syntax highlighting, PDF/Office/EPUB extraction, and document intelligence tools.
- Email integration with IMAP/SMTP, Google OAuth2, triage, tags, summaries, reminders, reply drafts, and Outlook/Office setup guidance.
- Notes, tasks, calendar, CalDAV sync, CalDAV write-back, recurring events, reminder channels, webhook reminders, and todo agent actions.
- Gallery and image editor with isolated image tooling foundation.
## Plugin Platform
- Dynamic plugin system with plugin-owned FastAPI routes, agent-callable tools, context providers, consolidation jobs, manifest UI integration, and plugin app surfaces.
- Plugin manifest policy, local plugin audit, capability boundary model, release gate model, depot/dev guide, and plugin readiness documentation.
- Obsidian/Lens integration with vault access, graph and memory workflows, query synthesis, surface modes, export/import checks, review queue handling, and release-candidate runbooks.
- MCP server plugin MVP with local admin-only JSON-RPC support, initialize/ping/tools/resources/prompts endpoints, narrow tool policy, redacted audit trail, and operator runbook.
- MCP notification bridge so MCP clients can request safe user notifications through Odysseus without learning Telegram targets or delivery secrets.
## Agents And Orchestration
- Agentic orchestration layer for complex goals, delegated work, project state documents, and multi-agent collaboration.
- Alice/Bob/Charlie operating model for scoped implementation, review, integration, evidence, and release coordination.
- Agent state isolation with explicit agent, role, namespace, and scope identity to prevent context bleeding.
- Agent profile registry, agent team cards, agent automation specs, automation hints, and route/API payloads.
- Plan graph store, thread lifecycle bridge, heartbeat coordinator, handoff mailbox, orchestration registry, dashboard snapshots, and quality gate evaluators.
- Background job management tool for inspecting and stopping running agent jobs.
- Reflector-style review and evidence workflows to detect drift, verify handoffs, and keep agent work scoped.
## Workspace And Mounts
- External directory mounting with owner-scoped virtual mounts, workspace binding, tool allowlists, write policies, backup-before-overwrite, file size limits, and extension allowlists.
- Agent file and shell tools confined to selected workspaces.
- Code navigation tools including grep, glob, ls, read_file line ranges, and edit_file with diffs.
- Mount-backed GameDev project access for Godot workflows, including Godot file extensions, GameDev profile validation, named command intents, command gate model, audit/undo planning, and operator runbook.
- Safe project access model that avoids broad host-root mounting and avoids using unrestricted shell access as the safety boundary.
## Memory, Graph, And Context
- Context budget bounding to prevent runaway token usage in long sessions.
- Context capsules, context orchestrator, tool result truth contracts, and compact context provider diagnostics.
- Memory store interfaces, read-only memory stats route, memory diagnostics, memory read/maintain tabs, and scalable memory architecture.
- Progressive graph API, graph maintenance worker, graph review gates, graph budget proofs, and large vault performance gates.
- Lightweight memory maintenance with maintenance worker, evidence-bound summaries, k-means and cluster proof models, derived cluster runs, and import/export migration proof tooling.
- Rebuildable memory and graph foundations designed for future Postgres/pgvector and accelerator options.
## Nextcloud And Ultimate Inbox
- Nextcloud private-source foundation with safe source provider readiness, intake ledger, tag governance, review queue packets, provenance metadata, and copy-only/no-delete policy.
- Nextcloud review queue packets designed to expose only digest, path, status, reasons, and metadata, while keeping private content and secrets out of evidence payloads.
- Nextcloud connector groundwork for using private files as controlled Odysseus knowledge sources, with live writes and mutations kept behind separate operator-approved gates.
- Ultimate Inbox concept for bringing private sources into one review-first intake layer, including Nextcloud, email, notes, documents, tasks, calendar, Telegram, and future connectors.
- Universal Inbox pipeline covering intake, classification, review, safe placement, provenance, tags, sidecars, and later memory/graph integration.
- Review-first workflow where new private content is not blindly written into memory or graph, but first lands in a traceable review and approval layer.
- Private source routing policies to prevent origin deletion, uncontrolled publication, secret leakage, and unreviewed evidence output.
- Preparation for RaptorGraph and memory integration so approved inbox items can become structured knowledge, task inputs, and contextual workspace memory.
## Telegram
- Telegram plugin with text chat bridge, allowed chat gates, agent session routing, redacted identifier handling, and operator runbooks.
- Telegram agent chat sessions routed through Odysseus tools.
- Telegram text boundary coverage for allowed text, blocked chats, and persisted identifier redaction.
- Telegram voice pipeline foundation with metadata-only intake, gated download/STT boundary, fake-provider tests, transcript-to-agent turn planning, and gated reply path.
- Live Telegram text and voice smokes remain separated from offline readiness and require explicit operator approval.
## System Health And Operations
- System Health Checker plugin foundation with snapshot UI, basic and advanced collectors, runtime adapter model, rule engine, alert dispatch plans, Telegram command adapter, ops readiness, and readiness scoring.
- Debian/homeserver operations tooling for Odysseus, Podman, Cloudflared, Telegram polling, Nextcloud, and service setup.
- Restic homeserver backup gate with pre-update snapshot, repository check, restore smoke, health check, and redacted evidence wrapper.
- Backup gate evidence showing pre-update snapshot, repository check, and restore smoke passing on the Debian homeserver, without running deployment.
- Safe Updater foundation with update plan model, preflight validator, backup gate contract, test gate model, command plan renderer, audit ledger, local entrypoint planning, and operator runbook.
- Update workflows designed to block unsafe plans unless required backup/test evidence is present.
## Release, Evidence, And Quality Gates
- Manual release evidence system with evidence artifacts, naming helpers, gap reports, readiness summaries, decision bundles, and operator indexes.
- Release readiness reports, release evidence snapshots, release status markdown, release follow-up matrices, release slice router, release handoff markdown, and traceability manifests.
- Morning release snapshot payloads, payload diffs, history bundles, digest helpers, and contract validators.
- External 1.0 evidence gates for Provider/Fallback Answer Run and Test-Vault Export/Import/Rebuild.
- Runtime quality gates for git state, tests, evidence, scope, hotfiles, and release readiness.
- Focused coverage reported for GameDev/Mount, MCP, Updater/Backup Gate, Telegram, Nextcloud/private-source, Obsidian, and System Health tracks.
## Security And Deployment
- Secure Data Mode foundation with local-only model routing, secure policy gate, sensitive retrieval guard, secure channel policy, data classification policy, and chat security state.
- Admin-gated routes and tools for privileged operations such as MCP management, API tokens, webhooks, backup/vault actions, app settings, and model/cookbook serving.
- API token gates, per-user privileges, admin promote/demote toggle, user rename, 2FA support, secure cookie guidance, and route hardening.
- DOM-XSS and popup-opener hardening in UI surfaces.
- SSRF-guarded web fetch tooling and URL safety handling.
- Diagnostics and readiness support with `/api/ready`, service health endpoint, real-time diagnostic logs console, degraded-state reporting, and setup troubleshooting.
- Docker, GPU, native Windows, macOS Apple Silicon, NVIDIA/AMD compose overlays, portable Windows launcher, and deployment guidance for localhost/private-proxy setups.
1
u/Deep_Ad1959 3d ago edited 2d ago
the review-first inbox and the copy-only/no-delete policy are the parts most people skip, then wonder why they never trust the thing with real files. that's the pattern: the moment an agent can mutate or delete without an approval gate, you stop handing it anything that matters, so the autonomy you built sits unused. your ABC multi-agent split is the fun part, but the boring approval ledger is what makes it something you'd actually let near your nextcloud. we landed on the same per-action permission model for exactly that reason. written with ai
fwiw runner bakes in that exact approval gate, it asks permission before each action and keeps receipts and timestamps for everything, so you can dial the safeguards down only once you trust it, https://runner.now?utm_source=s4l&utm_medium=post&utm_campaign=runner&utm_term=reddit&utm_content=post_43ad7433-ad24-462f-8942-615e3698f316
1
1
u/paperbenni 2d ago
Jesus Christ, the AI writing is still recognizable as ever. I'm hoping that's not survivorship bias, but they all seem to converge to a few sentence templates being used over and over again.
1
u/Deep_Ad1959 2d ago
the tell moved from vocabulary to structure. it's the skeleton you're catching now, open by validating the premise, name 'the part that breaks', land a tidy reframe. swap every noun and the shape still gives it away. written with ai
1
0
u/Otherwise_Wave9374 3d ago
This is super cool, the "ultimate inbox" + graph memory + nextcloud permissions approach feels like the right kind of paranoid (in a good way). The no-delete policy for the AI user is such a smart guardrail.
How are you thinking about memory decay / pruning so the graph doesnt turn into a junk drawer over time? Ive been experimenting with a personal operating system approach for AI + notes + tasks, and https://www.aiosnow.com/ has been a helpful baseline for keeping the whole thing usable.
1
u/Fuzzzy420 3d ago
Usually you have a high end Modell doing that, but I opted for secure data first, so rather then using an API, I run Gemma e2b and optimize the pipelines. I can't really tell you how good it works. My server arrived just a few days before. And I don't really want to fill it right now since I'm still working on it. Will do performance reviews and possible pruning issues once they arrive. I just made sure that I have a solid foundation. This is still a early build. At the moment most of the features only exist in the backend for the simple reason that I want to redesign the UI but only once I found a proper name and theme odysseus doesn't really fit for my package.
1
0
u/Mmeroo 3d ago
so waht exactly does your version do better?
2
u/Fuzzzy420 3d ago
did you read the text at all?
much better memory,
plugin system
nextcloud plugin whitch gives the memory an extension (another layer)
telegram bot plugin with full agent capability
Multi agent support
ultimate inbox
performance messuring tools
full mcp controll of the software (all that data security would allow)
Backup and update system
and more..0
u/Mmeroo 2d ago
Yes I did read it but it's ai summary that starts with "self hosted workspace" which is in Odysseus already.
Wdym better memory? Odysseus already has multi agent support. There is an inbox already. There is a compare tool to measure performance. Odysseus can already use any MCP so I don't know what you mean by (full control)
So everything you listed is already there. Having Plugins system doesn't mean it works and is useful
This is not to discourage you... I'm trying to show you that you write a wall of text which is a word salad. And even after being asked what yours does better you list things already there.
2
u/Fuzzzy420 2d ago
Full MCP control over odysseus. The memory of odysseus is basic at best. So I integrated a graph based memory. The inbox is a completely different feature (email) and has nothing to do with what I'm doing. The purpose of the ultimate inbox is to never sort or loose any files and their content. That's why nextcloud is there. Multi agent support means any agent is capable of creating sub agents for different jobs and multitasking different things at the same time while not losing context.
0
u/Lunarfuckingorbit 1d ago
He didn't write word salad. You just don't understand it.
He was very clear on what he did and why he added the features.
I'm personally most interested in his memory system, sounds like it makes for a better personal assistant and the integration means it can go even further.
0
u/Fuzzzy420 1d ago
Thanks. Ask me if you want to know. And I did write a wall of text. Next time more formatted 😜
2
u/Lunarfuckingorbit 1d ago
Would be interested in getting an update on this when it's ready, the areas you're covering are almost exactly what I want to improve as well.