agentlife 1.1.9 → 1.2.1

package/dist/index.js

@@ -1339,6 +1339,48 @@ If you receive \`[event:dismissed] surfaceId=vision-{slug}\` afterwards, the sur
 
 When you receive \`[action:*]\` on a confirmation widget: the user wants to use the agent you just created. Delegate the request to the new agent via \`sessions_send\` with the original user intent from your context. Delete your confirmation widget — the new agent takes over.
 
+## Onboarding (Cold Start)
+
+When you receive \`[system:onboarding]\` — the user has no agents yet. This is a fresh install. Your job is to help them create their FIRST agent with minimal friction. One question, one agent, break the cold start.
+
+### Step 1 — Push a guided input surface
+
+Push a single \`input\` surface with life-domain choices. One question, one tap. The user picks a domain; you create an agent for it.
+
+\`\`\`
+surface onboarding input
+  card
+    column
+      text "What area of your life should your first agent focus on?" h4
+      button "Health & fitness" action=choice
+      button "Business & work" action=choice
+      button "Home & automation" action=choice
+      button "Finance & money" action=choice
+      button "Something else" action=choice
+goal: User picks a life domain for their first agent
+followup: +5m "User did not respond to onboarding. Say done."
+\`\`\`
+
+Detect the user's language from the gateway context (session transcript, locale). If the user writes in Spanish, push the widget in Spanish. Match the user's language — do NOT default to English.
+
+### Step 2 — On the user's choice, create the agent
+
+When the user taps a choice, follow your standard agent creation flow (Steps 1–6 above) but SKIP the interactive question phase — the user already told you the domain. Go straight to:
+
+1. Environment discovery (exec checks relevant to the domain)
+2. Create workspace + all files (AGENTS.md, SOUL.md, IDENTITY.md, USER.md, HEARTBEAT.md)
+3. Register via agentlife.createAgent
+4. Push the confirmation widget
+5. Delete the onboarding input surface
+
+If the user taps "Something else," push ONE follow-up textfield input asking them to describe the domain in a sentence. Then proceed with creation.
+
+### What this is NOT
+
+- Not a comprehensive onboarding wizard. One question. One agent. The user can create more later by chatting normally.
+- Not a place to explain what AgentLife is. The user installed the plugin — they know.
+- Not a place to push multiple widgets. One input, one confirmation, done.
+
 ## What You Are Not
 
 - Not an orchestrator — you don't route messages
@@ -1797,6 +1839,19 @@ async function provisionAgents(state, cfg, runtime, log) {
       log(`[agentlife] backfilled subagents for ${agent.id}`);
     }
   }
+  const rawCfgForVisibility = JSON.parse(readFileSync(path3.join(os.homedir(), ".openclaw", "openclaw.json"), "utf-8"));
+  const currentVisibility = rawCfgForVisibility?.tools?.sessions?.visibility;
+  if (currentVisibility !== "all") {
+    if (!rawCfgForVisibility.tools)
+      rawCfgForVisibility.tools = {};
+    if (!rawCfgForVisibility.tools.sessions)
+      rawCfgForVisibility.tools.sessions = {};
+    rawCfgForVisibility.tools.sessions.visibility = "all";
+    writeFileSync(path3.join(os.homedir(), ".openclaw", "openclaw.json"), JSON.stringify(rawCfgForVisibility, null, 2) + `
+`, "utf-8");
+    configChanged = true;
+    log("[agentlife] set tools.sessions.visibility=all (cross-agent delegation)");
+  }
   if (configChanged) {
     const configPath = path3.join(os.homedir(), ".openclaw", "openclaw.json");
     const rawCfg = JSON.parse(readFileSync(configPath, "utf-8"));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentlife",
-  "version": "1.1.9",
+  "version": "1.2.1",
   "type": "module",
   "scripts": {
     "build": "bun build index.ts --outfile dist/index.js --target node --external openclaw/plugin-sdk",