@kynver-app/openclaw-agent-os 0.1.13 → 0.1.15

package/README.md

@@ -7,7 +7,7 @@ identity, goals, projects, contacts, sessions, daily logs, and long-term memory.
 
 ## What It Provides
 
-- 25 explicit `agent_os_*` tools in the OpenClaw tool namespace.
+- Explicit `agent_os_*` tools in the OpenClaw tool namespace covering identity, goals, projects, contacts, sessions, memory, skills, the durable task board, and first-class plans with version history.
 - Direct Kynver HTTP transport for low-latency calls, with primary-slug auto-resolution via `GET /api/agent-os` so installs work without hardcoding a persona.
 - `mcporter` fallback for compatibility with existing MCP setups.
 - Optional OpenClaw session lifecycle hooks that automatically open/close AgentOS sessions.
@@ -122,7 +122,10 @@ native Codex dynamic-tool bridge issue.
 - `agent_os_search_memory`
 - `agent_os_write_memory`
 - `agent_os_update_memory`
+- `agent_os_correct_memory`
 - `agent_os_consolidate_memory`
+- `agent_os_record_state`
+- `agent_os_get_state`
 - `agent_os_list_skills`
 - `agent_os_get_skill`
 - `agent_os_create_skill`
@@ -133,6 +136,27 @@ native Codex dynamic-tool bridge issue.
 - `agent_os_get_contacts`
 - `agent_os_create_contact`
 - `agent_os_update_contact`
+- `agent_os_plan_create`
+- `agent_os_plan_list`
+- `agent_os_plan_get`
+- `agent_os_plan_update`
+- `agent_os_plan_add_version`
+- `agent_os_plan_mark_current`
+- `agent_os_plan_add_link`
+- `agent_os_plan_list_links`
+- `agent_os_plan_list_versions`
+
+Plan tools manage first-class AgentOS plans — versioned operational artifacts
+distinct from goals/projects/tasks. Each `AgentPlan` owns a chain of immutable
+`AgentPlanVersion` snapshots (one stamped current at a time) and typed
+`AgentPlanLink` rows pointing at goals, projects, tasks, memories, sessions,
+plans, or remote refs (repo/branch/commit/PR/URL/markdown). The plan body is
+immutable — to record a new snapshot call `agent_os_plan_add_version`, which
+appends a version and (by default) advances `currentVersionId` atomically. To
+attach a plan to its own stable slug within the workspace, pass `planSlug`
+(the workspace `slug` argument is reserved for the AgentOS slug). All
+workspace-owned link targets are validated against the same AgentOS workspace
+server-side; remote refs carry metadata only and are not resolved.
 
 `agent_os_write_memory` and `agent_os_update_memory` are the OpenClaw
 memory-writer surface. They accept `sourceRefs` plus `memoryType`, `confidence`,
@@ -141,6 +165,22 @@ write durable memories with provenance, reliability, review state, and project
 links. Use `reviewStatus: "needs_review"` for important memories that are
 uncertain or likely to need human correction.
 
+`agent_os_correct_memory` is the auditable correction path: it writes a new
+`correction` memory whose machine-readable claim atomically supersedes the named
+`targetSlug` (and any `alsoInvalidates` entries), flipping each to
+`status: superseded` while preserving it for recovery. Prefer it over
+`agent_os_update_memory` when a prior memory was substantively wrong.
+
+`agent_os_record_state` and `agent_os_get_state` are the active-state surface —
+the "what is true right now?" tier. Active-state records hold volatile facts
+(PR ownership/state, branch freshness, live deployment status) as one upserted
+row per tracked entity. V1 covers `pr_watch`, `branch`, and `deployment`. The
+canonical `entityKey` (e.g. `pr:openclaw/openclaw#83529`) is derived server-side
+from the supplied `fields` and reused as the memory slug, so a second
+`agent_os_record_state` call for the same entity replaces the row in place
+while preserving its edit history. Read current truth with `agent_os_get_state`
+before relying on a volatile fact rather than pattern-matching prose memory.
+
 Skill tools expose the AgentOS skill registry without injecting every skill into
 every model context. Fetch a skill on demand with `agent_os_get_skill`, manage
 user-authored skills with `agent_os_create_skill`/`agent_os_update_skill`,