@kynver-app/openclaw-agent-os 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md ADDED
@@ -0,0 +1,104 @@
1
+ # @kynver-app/openclaw-agent-os
2
+
3
+ OpenClaw plugin that exposes Kynver AgentOS as first-class agent tools.
4
+
5
+ This package is the OpenClaw-native bridge for agents that use Kynver as their operating memory:
6
+ identity, goals, projects, contacts, sessions, daily logs, and long-term memory.
7
+
8
+ ## What It Provides
9
+
10
+ - 17 explicit `agent_os_*` tools in the OpenClaw tool namespace.
11
+ - Direct Kynver HTTP transport for low-latency calls.
12
+ - `mcporter` fallback for compatibility with existing MCP setups.
13
+ - Optional OpenClaw session lifecycle hooks that automatically open/close AgentOS sessions.
14
+ - `agent_os_health_check` for setup verification.
15
+
16
+ ## Install
17
+
18
+ ```bash
19
+ openclaw plugins install @kynver-app/openclaw-agent-os
20
+ ```
21
+
22
+ If your OpenClaw install does not support package installs yet, install this package into the OpenClaw
23
+ extensions directory and enable the plugin from there. The runtime entry point is `dist/index.js`.
24
+
25
+ ## Configure
26
+
27
+ Recommended direct HTTP config:
28
+
29
+ ```json
30
+ {
31
+ "plugins": {
32
+ "config": {
33
+ "kynver-agent-os-tools": {
34
+ "kynverApiUrl": "https://www.kynver.com",
35
+ "kynverApiKey": "kynver_xxx",
36
+ "agentOsSlug": "ghost",
37
+ "enableDirectHttp": true,
38
+ "enableSessionLifecycle": true
39
+ }
40
+ }
41
+ }
42
+ }
43
+ ```
44
+
45
+ Prefer OpenClaw secret references or environment-backed config for `kynverApiKey` when your install supports it.
46
+
47
+ Compatibility config through an existing `mcporter.json` still works:
48
+
49
+ ```json
50
+ {
51
+ "plugins": {
52
+ "config": {
53
+ "kynver-agent-os-tools": {
54
+ "agentOsServer": "kynver-agent-os",
55
+ "mcporterConfigPath": "/home/me/.openclaw/workspace/config/mcporter.json"
56
+ }
57
+ }
58
+ }
59
+ }
60
+ ```
61
+
62
+ ## Verify
63
+
64
+ Ask OpenClaw to run:
65
+
66
+ ```text
67
+ Use agent_os_health_check with my AgentOS slug.
68
+ ```
69
+
70
+ Expected healthy response:
71
+
72
+ - `ok: true`
73
+ - `status: "available"`
74
+ - `transport: "direct-http"` when `kynverApiUrl` is configured
75
+ - counts for goals/projects/contacts/memory stats
76
+
77
+ ## Tools
78
+
79
+ - `agent_os_health_check`
80
+ - `agent_os_get_context`
81
+ - `agent_os_open_session`
82
+ - `agent_os_close_session`
83
+ - `agent_os_log_session`
84
+ - `agent_os_list_goals`
85
+ - `agent_os_update_goal`
86
+ - `agent_os_get_projects`
87
+ - `agent_os_create_project`
88
+ - `agent_os_update_project`
89
+ - `agent_os_search_memory`
90
+ - `agent_os_write_memory`
91
+ - `agent_os_update_memory`
92
+ - `agent_os_consolidate_memory`
93
+ - `agent_os_get_contacts`
94
+ - `agent_os_create_contact`
95
+ - `agent_os_update_contact`
96
+
97
+ ## Development
98
+
99
+ ```bash
100
+ npm run typecheck -w @kynver-app/openclaw-agent-os
101
+ npm run build -w @kynver-app/openclaw-agent-os
102
+ ```
103
+
104
+ The plugin id remains `kynver-agent-os-tools` so existing OpenClaw configs continue to load the same tool surface.