Repository navigation
Agentlas OS 1.2.98
·
2 commits
to main
since this release
agentlas-os-channel: stable
- Memory is kept in four separate places: personal (about you), agent (what one agent learned that holds across projects), project (what is true only inside one project) and session (what is needed to continue one conversation). The engine reads across the places an owner has and answers with one recall rule on every surface. Nothing is moved by this update; a converted layout is switched on only by the Agentlas desktop app, one time, when it asks.
- Memory writes are one call: the model doing the work adds, rewrites, condenses or removes lines itself with
memory.record, and a guess about the person is never stored as a fact about them. The session-end hook records the turn and starts nothing; no model is named for memory work. - Agent folders live under
~/.agentlas/agents(override withAGENTLAS_AGENT_HOME).hephaestus register-agent <ref>registers a Hub or Cloud agent on this computer and gives it a folder, and the engine answers whether an agent can be used right now (not_registered,no_folderand so on) so every host says the same words. - A newly created project marker carries its own unique id, so two projects with the same folder name need not share one key. A project's code index can live with that project's memory.
- Windows: the memory tree opens with the extended-path prefix, so a long user name no longer breaks memory reads and writes past 259 characters.
- A forget that did not finish is carried until it does, and a forget reaches only the owner of the forgotten line. A hook that cannot read everything now says so instead of answering nothing.
- Compatibility: after the desktop app converts a memory store (store schema version 2), engines 1.2.96 and 1.2.97 do not open that store and keep working without memory until updated. Update the engine before opening the 2.0 desktop app.