Persistent Context / Task Maxer for long-running agents (and a lot of shit. Such as GGI, Good General intelligence))

[Zyrix007]

(yes, I had AI write it all. But I did some review on it.)

Hey Felix — I have a somewhat abstract architecture idea that I thought might be relevant to the kind of local/self-hosted agent system you're building with Odysseus.

I want to be clear up front: I don't have a working implementation yet, and I'm not presenting this as a finished solution or asking Odysseus to integrate it.

The idea is a Persistent Context Manager, with a task-oriented component I call Task Maxer.

The basic premise is:

Models/workers are temporary; task state should be persistent.

Instead of making an agent reconstruct a long project from its entire conversation history, a persistent task record would maintain things such as:

• confirmed specification and constraints
• current status and assignments
• decisions and open questions
• blockers/dependencies
• relevant artifacts
• verification state
• execution receipts/history

Different workers could then read only the state relevant to their assignment. A worker could disappear, be replaced by another model, or be upgraded without the replacement having to reconstruct the whole conversation.

I'm also thinking of extending this into a broader persistent context system:

User/Profile Context → Memory → Task State → Projects/Artifacts → Receipts/Audit

with per-user application-managed storage, worker-specific state views, and an exportable user-owned data layer. A local deployment could potentially put the persistent store on a NAS while clients/models remain on different machines.

The other reason I find it interesting is that it connects several agent patterns: specialist workers, multiple instances of the same specialist, sibling/critic workers, verification, temporary teams, model replacement, and long-running projects.

I've written the architecture out in more detail in the attached document.

(I have a friend who introduced me to coding and i thought might do some thinking about my-to-be project in advance. It has many ideas which currently exists. They just needs to be re-arranged. So, if it's not clear enough. I DON'T KNOW HOW TO ACTUALLY CODE. I am a bachelor, currently doing bachelors in both business administration and law, at the same time. With amateur future interest in coding and AI.
ZyroG2i_Master_Notes_vNext.docx )

No pressure to respond — I just thought the overlap with Odysseus was interesting.

@pewdiepie-archdaemon

[touzenesmy]

Hello,
Not Felix here but I have something that I've already implemented.
One skill named skill management skill. Everytime a skill operation is called, it gets read.

• Asks the user (if the user hasn't said it explicitly) before creating a skill
• Make the skills read protected by a prompt saying that every skill update has to be done according to the skill management skill
• The skill management skill requires that every skill has to be versionned, backed up, reread twice, tested and if confirmed working published

Now the important part:

• If the still is related to a project, the project directory has to be mentionned in the skill
• One and only one memory has to be created for each skill for sensitive information related to the user, the skill is generic methodology
• Every project has to have a documentation folder, containing :

1. The project description
2. The project files and what they do
3. A changelog for every version and work that has been done
4. The project architecture if its complex
5. A todolist if not existent
6. Other things I've might forgot

• The skill must know all the difficulties encountered and how X and Y were solved and keep the methodology
• Other releavant informations that I've forgot

This way, every time I open a new session, I just say for example let's continue working on X project. Everything gets read and picked up and ready to go
Also I've took inspiration from many people who basically have been working on complex projects, I am willing to share if needed

Here, I've attached my project and skills management skill. I would argue they could be/should be part of odysseus itself for a better management of skills, memories and projects for users.
skillmanagementskill.md
projectmanagementskill.md