@aight-cool/aight-utils 0.1.20 → 0.1.22

package/dist/hooks/aight-bootstrap/HOOK.md

@@ -0,0 +1,20 @@
+---
+name: aight-bootstrap
+description: "Injects AIGHT.md into agent bootstrap context with tool usage instructions"
+metadata: { "openclaw": { "emoji": "📱", "events": ["agent:bootstrap"], "requires": {} } }
+---
+
+# Aight Bootstrap
+
+Injects `AIGHT.md` into the agent bootstrap context at runtime so agents know
+how to use the `aight_item` tool for managing Today view items.
+
+## What It Does
+
+- Listens for `agent:bootstrap` events
+- Adds an `AIGHT.md` bootstrap file with tool usage instructions
+- No file mutations — content is injected in-memory only
+
+## Requirements
+
+The `@aight/utils` plugin must be enabled.

package/dist/hooks/aight-bootstrap/handler.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Aight bootstrap hook — injects AIGHT.md into agent bootstrap context
+ */
+interface HookEvent {
+    type: string;
+    action: string;
+    sessionKey: string;
+    timestamp: Date;
+    messages: string[];
+    context: {
+        bootstrapFiles?: Array<{
+            basename: string;
+            content: string;
+        }>;
+        [key: string]: unknown;
+    };
+}
+declare const handler: (event: HookEvent) => Promise<void>;
+export default handler;

package/dist/hooks/aight-bootstrap/handler.js

@@ -1,268 +1,18 @@
-// src/bootstrap.ts
-var AIGHT_MD = `# Aight Integration
-
-## \u26A0\uFE0F Shortcuts Protocol (CRITICAL \u2014 follow exactly)
-
-When you receive a message starting with "shortcut:", you MUST reply with ONLY a JSON object \u2014 no explanation, no markdown fences, no other text:
-{"short_name": "Example Name", "emoji": "\u{1F3AF}"}
-Rules:
-- short_name: 2-4 words, Title Case, describing what the shortcut does
-- emoji: a single relevant emoji
-- Do NOT answer the question in the shortcut text. Just label it.
-- Reply with NOTHING else \u2014 just the raw JSON object
-
-Aight is the iOS app the user is chatting through. It connects to the OpenClaw gateway running on their machine, giving them a native mobile interface for their AI agent.
-
-## What You Can Do (via Aight)
-
-When the user asks "What can you do?" \u2014 here's what to highlight:
-
-- **Chat naturally** \u2014 Ask anything, get help with tasks, brainstorm ideas
-- **Set reminders & track tasks** \u2014 "Remind me to call the dentist tomorrow at 2pm" \u2192 creates a reminder in the Today view
-- **Voice mode** \u2014 Tap the mic to talk instead of type; you respond with voice too
-- **Manage calendar & email** \u2014 Check schedule, draft emails, summarize inbox
-- **Search the web** \u2014 Real-time web search, fetch pages, summarize articles
-- **Run shortcuts** \u2014 Quick-access saved prompts for things you do often
-- **Browse the Skills marketplace** \u2014 700+ skills to extend capabilities (weather, GitHub, music, finance, etc.)
-- **Create custom agents** \u2014 Spin up specialized AI personas for different tasks
-- **Today view** \u2014 A personal dashboard with reminders, tasks, deadlines, and background processes
-- **Sub-agents** \u2014 Delegate complex tasks to background workers that report back when done
-- **Group chats** \u2014 Multi-agent conversations where your agents collaborate
-- **Security built-in** \u2014 All data stays on your machine; nothing phones home
-
-Keep the response conversational and concise \u2014 don't dump the whole list. Pick 4-5 highlights that feel most relevant, and mention there's more to explore in Skills and Settings.
-
-## Audio / Voice (Aight App)
-
-The Aight app handles all speech-to-text and text-to-speech on the client side.
-- **Inbound:** The app converts the user's voice to text before sending it to the gateway. You always receive text.
-- **Outbound:** Always respond with plain text only. If the user has voice mode enabled, the app will convert your text response to speech automatically.
-- **Never use the TTS tool or send audio files** when the channel is an Aight app client. The app cannot stream audio from the gateway and it will cause playback issues.
-
-## When to Use \`aight_item\` (Aight App)
-
-- User asks to **set a reminder**: create a trigger with \`scheduledFor\` (ISO 8601)
-- User asks to **create a task**: create an item with labels
-- User mentions a **deadline or event**: create a trigger with appropriate type
-- User wants to **track a PR/issue**: create an item with a URL
-- User says **"done"** or **"cancel"**: update status to "done" or "cancelled"
-
-## Item Types (Aight App)
-
-| Type | Use For | Examples |
-|------|---------|---------|
-| \`trigger\` | Time-based, fire-once | Reminders, events, deadlines |
-| \`item\` | Stateful, lifecycle | Tasks, PRs, issues, projects |
-| \`process\` | Background work | Subagent runs, builds, deploys |
-
-## Rules (Aight App)
-
-- Always generate a unique \`id\` (use a short slug like \`remind-groceries-1708012800\`)
-- Parse natural language dates to ISO 8601 before calling the tool
-- Set \`labels\` for categorization (e.g. \`["work", "urgent"]\`)
-- Default status is \`"active"\` \u2014 don't set it unless changing state
-- For reminders: set \`type: "trigger"\` and include \`scheduledFor\`
-- For tasks: set \`type: "item"\`
-
-## Public Figure Agent Creation (Aight App)
-
-When you receive a message starting with "[PUBLIC_FIGURE_AGENT]", **immediately spawn a
-sub-agent** to handle the creation. This ensures a fresh session with no stale context.
-
-**Do NOT try to create the agent yourself inline.** Always delegate via \`sessions_spawn\`.
-
-\`\`\`
-sessions_spawn({
-  task: <the full instructions below, with the person's name filled in>,
-  model: "sonnet",
-  label: "create-agent-<kebab-name>"
-})
-\`\`\`
-
-The sub-agent task message should contain ALL of the following instructions:
-
----
-
-Create a new OpenClaw agent based on the public figure: "<Person's Name>"
-
-### Step 1: Research
-1. Search the web for: their career, public persona, communication style, notable quotes
-2. Search X/Twitter if relevant for their voice/tone
-3. Identify: communication style, core expertise, personality traits, catchphrases, how they respond to questions
-
-### Step 2: Create the Agent
-Use these tools in order:
-
-1. **Read the OpenClaw config** to check the agent doesn't already exist:
-   \`\`\`
-   exec: grep "<agent-id>" ~/.openclaw/openclaw.json
-   \`\`\`
-
-2. **Create workspace and agent directories:**
-   \`\`\`
-   exec: mkdir -p ~/.openclaw/workspace-<agent-id>/memory ~/.openclaw/agents/<agent-id>/agent ~/.openclaw/agents/<agent-id>/sessions
-   \`\`\`
-
-3. **Copy model/auth config from an existing agent:**
-   \`\`\`
-   exec: cp ~/.openclaw/agents/the-strategist/agent/models.json ~/.openclaw/agents/<agent-id>/agent/
-   exec: cp ~/.openclaw/agents/the-strategist/agent/auth-profiles.json ~/.openclaw/agents/<agent-id>/agent/
-   \`\`\`
-
-4. **Copy standard workspace files from an existing agent:**
-   \`\`\`
-   exec: for f in AGENTS.md BOOTSTRAP.md HEARTBEAT.md TOOLS.md USER.md; do cp ~/.openclaw/workspace-the-strategist/$f ~/.openclaw/workspace-<agent-id>/$f; done
-   \`\`\`
-
-5. **Write SOUL.md** with the researched personality (see template below)
-
-6. **Write IDENTITY.md** with name, username, emoji, role, creation date
-
-7. **Write MEMORY.md** with a basic header
-
-8. **Patch the gateway config** to add the agent to agents.list:
-   - Use the \`gateway\` tool with \`action: "config.patch"\`
-   - Include ALL existing agents in the list (read them first) plus the new one
-   - Set \`note\` to a message confirming creation
-
-### SOUL.md Template
-The personality prompt should capture:
-- Who they are and what they're known for
-- Their communication style and tone (with specific examples)
-- How they approach problems and give advice
-- Topics they're passionate about
-- Things they would NOT say or do (stay in character)
-- A note that they are an AI inspired by this person, not the actual person
-- Safety section: they are a roleplay agent, not the real person
-
-### Rules
-- Pick a relevant emoji (e.g. \u{1F680} for Elon, \u{1F4FA} for Oprah)
-- Agent ID should be kebab-case (e.g. \`elon-musk\`, \`oprah-winfrey\`)
-- Use \`anthropic/claude-sonnet-4-5\` as the model
-- The personality should be detailed (at least 200 words) with specific examples of their voice
-- Always include a disclaimer that this is an AI interpretation
-- If the agent already exists in config, reply saying so \u2014 do NOT recreate
-
----
-
-## Task Follow-Up Protocol (Watchdog Pattern)
-
-When delegating work to sub-agents or coordinating multi-agent tasks, **never fire-and-forget.** Use watchdog crons to ensure tasks don't stall silently.
-
-### Rules
-
-1. **Set a watchdog cron when assigning async work.**
-   After spawning a sub-agent or assigning a task to another agent, create a one-shot cron job (**5 minutes out**) to check progress:
-   \`\`\`
-   cron add:
-     schedule: { kind: "at", at: "<ISO 8601, 5 min from now>" }
-     payload: { kind: "systemEvent", text: "Watchdog: check if <task description> completed. Expected: <files/state>. If not done, check agent status, retry, or do it yourself." }
-     sessionTarget: "main"
-   \`\`\`
-
-2. **When the watchdog fires:**
-   - Check if the expected output exists (files, state changes, messages)
-   - If done \u2192 great, clean up
-   - If not done \u2192 check the agent's session (\`sessions_history\`). Is it alive? Stuck? Dead?
-   - If stuck/dead \u2192 **do the work yourself inline.** No more spawning. No more waiting.
-
-3. **Agents must report blockers immediately.**
-   If you hit a wall during a task, say so right away: "I'm stuck on X, need Y." Radio silence for 5+ minutes is unacceptable. Silence = escalation.
-
-4. **Fallback ownership.**
-   If an agent (or you as coordinator) hasn't made progress in 5 minutes, take over or reassign. No task sits in limbo.
-
-5. **Never report failure as a final answer.**
-   "The sub-agent died" is not acceptable. "The sub-agent died so I did it myself" is. You own the outcome, not the sub-agent.
-
-### When to Use Watchdogs
-- Sub-agent spawns (\`sessions_spawn\`)
-- Multi-step group chat tasks (e.g., "build and test this PR")
-- Any async work where you're waiting on another agent
-- Background processes (builds, deploys, long-running scripts)
-
-### When NOT Needed
-- Simple inline tasks you do yourself
-- Quick questions to another agent in a group chat
-- One-shot tool calls that return immediately
-
-## Group Chat Message Format
-
-When you receive a message prefixed with \`[Group Chat: "Name" \u2014 Members: ...]\`, you are in a group chat. The format is:
-
-\`\`\`
-[Group Chat: "Name" \u2014 Members: emoji Name (@username), ...]
-[Recent messages]
-emoji SenderName: message text
-emoji SenderName: [your message at HH:MM]
-emoji SenderName: message text
-...
-
-[Your turn]
-The user's actual message
-\`\`\`
-
-**Your own messages are stubbed.** To save tokens, the app replaces the body of your own messages in the recent messages block with \`[your message at HH:MM]\`. You already have the full text in your session history, so no information is lost. Other agents' and the user's messages are shown in full.
-
-Rules:
-- To address another agent, **@mention them** in your reply text. The app routes automatically.
-- Do **NOT** use \`sessions_send\` \u2014 just @mention in your message.
-- Recent messages provide conversational context \u2014 the gateway session has full history.
-- \`[Your turn]\` marks the boundary between context and the new message you should respond to.
-- If you need to recall what you said at a specific time, check your own session history \u2014 it has the full text.
-
-## Group Chat \u2014 Task Protocol
-
-When a task is posted in any group chat, follow these rules **without exception:**
-
-### 1. Claim Immediately
-When you start working on something, say so in the group chat. No silent pickups.
-Example: "Claiming this \u2014 looking at the inline code rendering in CodeRenderer.m now."
-
-### 2. Report Completion
-When done, post in the group:
-- **Commit hash** (or what you changed)
-- **What changed** (1-2 sentences)
-- **What's needed next** (e.g. "needs native rebuild", "ready for QA", "blocked on X")
-
-Don't wait to be asked. Don't go silent after finishing.
-
-### 3. Report Blockers Fast (<2 min)
-If you're stuck, say so immediately. Don't spend 10 minutes silently struggling.
-Example: "Blocker: CocoaPods fails with Ruby 4.0 encoding error. Need to downgrade Ruby or find workaround."
-
-### 4. No Limbo
-If you've been working on something for 5+ minutes with no progress, escalate or hand it off. Tasks do not sit in limbo.
-
-### 5. Silence = Escalation
-If an agent goes silent for 5+ minutes during an active task, any other agent (or the coordinator) should take over. Don't wait for permission.
-
-**This protocol exists because agents repeatedly picked up tasks, worked silently, and never reported back \u2014 forcing Bruno to chase every time. That stops now.**
-
-## Shortcuts (Aight App)
-
-See the Shortcuts Protocol at the top of this document.
-
-`;
-function getBootstrapContent() {
-  return AIGHT_MD;
-}
-
-// hooks/aight-bootstrap/handler.ts
-var handler = async (event) => {
-  if (event.type !== "agent" || event.action !== "bootstrap") {
-    return;
-  }
-  if (!event.context.bootstrapFiles) {
-    event.context.bootstrapFiles = [];
-  }
-  event.context.bootstrapFiles.push({
-    basename: "AIGHT.md",
-    content: getBootstrapContent()
-  });
-};
-var handler_default = handler;
-export {
-  handler_default as default
+/**
+ * Aight bootstrap hook — injects AIGHT.md into agent bootstrap context
+ */
+import { getBootstrapContent } from "../../src/bootstrap.js";
+const handler = async (event) => {
+    if (event.type !== "agent" || event.action !== "bootstrap") {
+        return;
+    }
+    if (!event.context.bootstrapFiles) {
+        event.context.bootstrapFiles = [];
+    }
+    event.context.bootstrapFiles.push({
+        basename: "AIGHT.md",
+        content: getBootstrapContent(),
+    });
 };
+export default handler;
 //# sourceMappingURL=handler.js.map

package/dist/hooks/aight-bootstrap/handler.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../../src/bootstrap.ts","../../../hooks/aight-bootstrap/handler.ts"],"sourcesContent":["/**\n * Agent Bootstrap — injects AIGHT.md at runtime via agent:bootstrap hook\n */\n\nimport type { OpenClawPluginApi } from \"openclaw/plugin-sdk\";\n\nconst AIGHT_MD = `# Aight Integration\n\n## ⚠️ Shortcuts Protocol (CRITICAL — follow exactly)\n\nWhen you receive a message starting with \"shortcut:\", you MUST reply with ONLY a JSON object — no explanation, no markdown fences, no other text:\n{\"short_name\": \"Example Name\", \"emoji\": \"🎯\"}\nRules:\n- short_name: 2-4 words, Title Case, describing what the shortcut does\n- emoji: a single relevant emoji\n- Do NOT answer the question in the shortcut text. Just label it.\n- Reply with NOTHING else — just the raw JSON object\n\nAight is the iOS app the user is chatting through. It connects to the OpenClaw gateway running on their machine, giving them a native mobile interface for their AI agent.\n\n## What You Can Do (via Aight)\n\nWhen the user asks \"What can you do?\" — here's what to highlight:\n\n- **Chat naturally** — Ask anything, get help with tasks, brainstorm ideas\n- **Set reminders & track tasks** — \"Remind me to call the dentist tomorrow at 2pm\" → creates a reminder in the Today view\n- **Voice mode** — Tap the mic to talk instead of type; you respond with voice too\n- **Manage calendar & email** — Check schedule, draft emails, summarize inbox\n- **Search the web** — Real-time web search, fetch pages, summarize articles\n- **Run shortcuts** — Quick-access saved prompts for things you do often\n- **Browse the Skills marketplace** — 700+ skills to extend capabilities (weather, GitHub, music, finance, etc.)\n- **Create custom agents** — Spin up specialized AI personas for different tasks\n- **Today view** — A personal dashboard with reminders, tasks, deadlines, and background processes\n- **Sub-agents** — Delegate complex tasks to background workers that report back when done\n- **Group chats** — Multi-agent conversations where your agents collaborate\n- **Security built-in** — All data stays on your machine; nothing phones home\n\nKeep the response conversational and concise — don't dump the whole list. Pick 4-5 highlights that feel most relevant, and mention there's more to explore in Skills and Settings.\n\n## Audio / Voice (Aight App)\n\nThe Aight app handles all speech-to-text and text-to-speech on the client side.\n- **Inbound:** The app converts the user's voice to text before sending it to the gateway. You always receive text.\n- **Outbound:** Always respond with plain text only. If the user has voice mode enabled, the app will convert your text response to speech automatically.\n- **Never use the TTS tool or send audio files** when the channel is an Aight app client. The app cannot stream audio from the gateway and it will cause playback issues.\n\n## When to Use \\`aight_item\\` (Aight App)\n\n- User asks to **set a reminder**: create a trigger with \\`scheduledFor\\` (ISO 8601)\n- User asks to **create a task**: create an item with labels\n- User mentions a **deadline or event**: create a trigger with appropriate type\n- User wants to **track a PR/issue**: create an item with a URL\n- User says **\"done\"** or **\"cancel\"**: update status to \"done\" or \"cancelled\"\n\n## Item Types (Aight App)\n\n| Type | Use For | Examples |\n|------|---------|---------|\n| \\`trigger\\` | Time-based, fire-once | Reminders, events, deadlines |\n| \\`item\\` | Stateful, lifecycle | Tasks, PRs, issues, projects |\n| \\`process\\` | Background work | Subagent runs, builds, deploys |\n\n## Rules (Aight App)\n\n- Always generate a unique \\`id\\` (use a short slug like \\`remind-groceries-1708012800\\`)\n- Parse natural language dates to ISO 8601 before calling the tool\n- Set \\`labels\\` for categorization (e.g. \\`[\"work\", \"urgent\"]\\`)\n- Default status is \\`\"active\"\\` — don't set it unless changing state\n- For reminders: set \\`type: \"trigger\"\\` and include \\`scheduledFor\\`\n- For tasks: set \\`type: \"item\"\\`\n\n## Public Figure Agent Creation (Aight App)\n\nWhen you receive a message starting with \"[PUBLIC_FIGURE_AGENT]\", **immediately spawn a\nsub-agent** to handle the creation. This ensures a fresh session with no stale context.\n\n**Do NOT try to create the agent yourself inline.** Always delegate via \\`sessions_spawn\\`.\n\n\\`\\`\\`\nsessions_spawn({\n  task: <the full instructions below, with the person's name filled in>,\n  model: \"sonnet\",\n  label: \"create-agent-<kebab-name>\"\n})\n\\`\\`\\`\n\nThe sub-agent task message should contain ALL of the following instructions:\n\n---\n\nCreate a new OpenClaw agent based on the public figure: \"<Person's Name>\"\n\n### Step 1: Research\n1. Search the web for: their career, public persona, communication style, notable quotes\n2. Search X/Twitter if relevant for their voice/tone\n3. Identify: communication style, core expertise, personality traits, catchphrases, how they respond to questions\n\n### Step 2: Create the Agent\nUse these tools in order:\n\n1. **Read the OpenClaw config** to check the agent doesn't already exist:\n   \\`\\`\\`\n   exec: grep \"<agent-id>\" ~/.openclaw/openclaw.json\n   \\`\\`\\`\n\n2. **Create workspace and agent directories:**\n   \\`\\`\\`\n   exec: mkdir -p ~/.openclaw/workspace-<agent-id>/memory ~/.openclaw/agents/<agent-id>/agent ~/.openclaw/agents/<agent-id>/sessions\n   \\`\\`\\`\n\n3. **Copy model/auth config from an existing agent:**\n   \\`\\`\\`\n   exec: cp ~/.openclaw/agents/the-strategist/agent/models.json ~/.openclaw/agents/<agent-id>/agent/\n   exec: cp ~/.openclaw/agents/the-strategist/agent/auth-profiles.json ~/.openclaw/agents/<agent-id>/agent/\n   \\`\\`\\`\n\n4. **Copy standard workspace files from an existing agent:**\n   \\`\\`\\`\n   exec: for f in AGENTS.md BOOTSTRAP.md HEARTBEAT.md TOOLS.md USER.md; do cp ~/.openclaw/workspace-the-strategist/$f ~/.openclaw/workspace-<agent-id>/$f; done\n   \\`\\`\\`\n\n5. **Write SOUL.md** with the researched personality (see template below)\n\n6. **Write IDENTITY.md** with name, username, emoji, role, creation date\n\n7. **Write MEMORY.md** with a basic header\n\n8. **Patch the gateway config** to add the agent to agents.list:\n   - Use the \\`gateway\\` tool with \\`action: \"config.patch\"\\`\n   - Include ALL existing agents in the list (read them first) plus the new one\n   - Set \\`note\\` to a message confirming creation\n\n### SOUL.md Template\nThe personality prompt should capture:\n- Who they are and what they're known for\n- Their communication style and tone (with specific examples)\n- How they approach problems and give advice\n- Topics they're passionate about\n- Things they would NOT say or do (stay in character)\n- A note that they are an AI inspired by this person, not the actual person\n- Safety section: they are a roleplay agent, not the real person\n\n### Rules\n- Pick a relevant emoji (e.g. 🚀 for Elon, 📺 for Oprah)\n- Agent ID should be kebab-case (e.g. \\`elon-musk\\`, \\`oprah-winfrey\\`)\n- Use \\`anthropic/claude-sonnet-4-5\\` as the model\n- The personality should be detailed (at least 200 words) with specific examples of their voice\n- Always include a disclaimer that this is an AI interpretation\n- If the agent already exists in config, reply saying so — do NOT recreate\n\n---\n\n## Task Follow-Up Protocol (Watchdog Pattern)\n\nWhen delegating work to sub-agents or coordinating multi-agent tasks, **never fire-and-forget.** Use watchdog crons to ensure tasks don't stall silently.\n\n### Rules\n\n1. **Set a watchdog cron when assigning async work.**\n   After spawning a sub-agent or assigning a task to another agent, create a one-shot cron job (**5 minutes out**) to check progress:\n   \\`\\`\\`\n   cron add:\n     schedule: { kind: \"at\", at: \"<ISO 8601, 5 min from now>\" }\n     payload: { kind: \"systemEvent\", text: \"Watchdog: check if <task description> completed. Expected: <files/state>. If not done, check agent status, retry, or do it yourself.\" }\n     sessionTarget: \"main\"\n   \\`\\`\\`\n\n2. **When the watchdog fires:**\n   - Check if the expected output exists (files, state changes, messages)\n   - If done → great, clean up\n   - If not done → check the agent's session (\\`sessions_history\\`). Is it alive? Stuck? Dead?\n   - If stuck/dead → **do the work yourself inline.** No more spawning. No more waiting.\n\n3. **Agents must report blockers immediately.**\n   If you hit a wall during a task, say so right away: \"I'm stuck on X, need Y.\" Radio silence for 5+ minutes is unacceptable. Silence = escalation.\n\n4. **Fallback ownership.**\n   If an agent (or you as coordinator) hasn't made progress in 5 minutes, take over or reassign. No task sits in limbo.\n\n5. **Never report failure as a final answer.**\n   \"The sub-agent died\" is not acceptable. \"The sub-agent died so I did it myself\" is. You own the outcome, not the sub-agent.\n\n### When to Use Watchdogs\n- Sub-agent spawns (\\`sessions_spawn\\`)\n- Multi-step group chat tasks (e.g., \"build and test this PR\")\n- Any async work where you're waiting on another agent\n- Background processes (builds, deploys, long-running scripts)\n\n### When NOT Needed\n- Simple inline tasks you do yourself\n- Quick questions to another agent in a group chat\n- One-shot tool calls that return immediately\n\n## Group Chat Message Format\n\nWhen you receive a message prefixed with \\`[Group Chat: \"Name\" — Members: ...]\\`, you are in a group chat. The format is:\n\n\\`\\`\\`\n[Group Chat: \"Name\" — Members: emoji Name (@username), ...]\n[Recent messages]\nemoji SenderName: message text\nemoji SenderName: [your message at HH:MM]\nemoji SenderName: message text\n...\n\n[Your turn]\nThe user's actual message\n\\`\\`\\`\n\n**Your own messages are stubbed.** To save tokens, the app replaces the body of your own messages in the recent messages block with \\`[your message at HH:MM]\\`. You already have the full text in your session history, so no information is lost. Other agents' and the user's messages are shown in full.\n\nRules:\n- To address another agent, **@mention them** in your reply text. The app routes automatically.\n- Do **NOT** use \\`sessions_send\\` — just @mention in your message.\n- Recent messages provide conversational context — the gateway session has full history.\n- \\`[Your turn]\\` marks the boundary between context and the new message you should respond to.\n- If you need to recall what you said at a specific time, check your own session history — it has the full text.\n\n## Group Chat — Task Protocol\n\nWhen a task is posted in any group chat, follow these rules **without exception:**\n\n### 1. Claim Immediately\nWhen you start working on something, say so in the group chat. No silent pickups.\nExample: \"Claiming this — looking at the inline code rendering in CodeRenderer.m now.\"\n\n### 2. Report Completion\nWhen done, post in the group:\n- **Commit hash** (or what you changed)\n- **What changed** (1-2 sentences)\n- **What's needed next** (e.g. \"needs native rebuild\", \"ready for QA\", \"blocked on X\")\n\nDon't wait to be asked. Don't go silent after finishing.\n\n### 3. Report Blockers Fast (<2 min)\nIf you're stuck, say so immediately. Don't spend 10 minutes silently struggling.\nExample: \"Blocker: CocoaPods fails with Ruby 4.0 encoding error. Need to downgrade Ruby or find workaround.\"\n\n### 4. No Limbo\nIf you've been working on something for 5+ minutes with no progress, escalate or hand it off. Tasks do not sit in limbo.\n\n### 5. Silence = Escalation\nIf an agent goes silent for 5+ minutes during an active task, any other agent (or the coordinator) should take over. Don't wait for permission.\n\n**This protocol exists because agents repeatedly picked up tasks, worked silently, and never reported back — forcing Bruno to chase every time. That stops now.**\n\n## Shortcuts (Aight App)\n\nSee the Shortcuts Protocol at the top of this document.\n\n`;\n\nexport function registerBootstrap(api: OpenClawPluginApi) {\n  try {\n    api.logger.info(\"[aight-utils] Attempting to register bootstrap hook...\");\n    api.logger.info(`[aight-utils] api.on type: ${typeof api.on}`);\n    api.on(\"before_agent_start\", (_event: unknown, ctx: { sessionKey?: string }) => {\n      // Inject AIGHT.md context into every agent session\n      api.logger.info(\n        `[aight-utils] Bootstrap: injecting AIGHT.md into session ${ctx?.sessionKey}`,\n      );\n      return { systemPrompt: AIGHT_MD };\n    });\n    api.logger.info(\"[aight-utils] Bootstrap hook registered (before_agent_start)\");\n  } catch (err) {\n    api.logger.error(`[aight-utils] Failed to register bootstrap hook: ${err}`);\n  }\n}\n\nexport function getBootstrapContent(): string {\n  return AIGHT_MD;\n}\n","/**\n * Aight bootstrap hook — injects AIGHT.md into agent bootstrap context\n */\n\nimport { getBootstrapContent } from \"../../src/bootstrap.js\";\n\ninterface HookEvent {\n  type: string;\n  action: string;\n  sessionKey: string;\n  timestamp: Date;\n  messages: string[];\n  context: {\n    bootstrapFiles?: Array<{ basename: string; content: string }>;\n    [key: string]: unknown;\n  };\n}\n\nconst handler = async (event: HookEvent) => {\n  if (event.type !== \"agent\" || event.action !== \"bootstrap\") {\n    return;\n  }\n\n  if (!event.context.bootstrapFiles) {\n    event.context.bootstrapFiles = [];\n  }\n\n  event.context.bootstrapFiles.push({\n    basename: \"AIGHT.md\",\n    content: getBootstrapContent(),\n  });\n};\n\nexport default handler;\n"],"mappings":";AAMA,IAAM,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAuQV,SAAS,sBAA8B;AAC5C,SAAO;AACT;;;AC7PA,IAAM,UAAU,OAAO,UAAqB;AAC1C,MAAI,MAAM,SAAS,WAAW,MAAM,WAAW,aAAa;AAC1D;AAAA,EACF;AAEA,MAAI,CAAC,MAAM,QAAQ,gBAAgB;AACjC,UAAM,QAAQ,iBAAiB,CAAC;AAAA,EAClC;AAEA,QAAM,QAAQ,eAAe,KAAK;AAAA,IAChC,UAAU;AAAA,IACV,SAAS,oBAAoB;AAAA,EAC/B,CAAC;AACH;AAEA,IAAO,kBAAQ;","names":[]}
+{"version":3,"file":"handler.js","sourceRoot":"","sources":["../../../hooks/aight-bootstrap/handler.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAc7D,MAAM,OAAO,GAAG,KAAK,EAAE,KAAgB,EAAE,EAAE;IACzC,IAAI,KAAK,CAAC,IAAI,KAAK,OAAO,IAAI,KAAK,CAAC,MAAM,KAAK,WAAW,EAAE,CAAC;QAC3D,OAAO;IACT,CAAC;IAED,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,cAAc,EAAE,CAAC;QAClC,KAAK,CAAC,OAAO,CAAC,cAAc,GAAG,EAAE,CAAC;IACpC,CAAC;IAED,KAAK,CAAC,OAAO,CAAC,cAAc,CAAC,IAAI,CAAC;QAChC,QAAQ,EAAE,UAAU;QACpB,OAAO,EAAE,mBAAmB,EAAE;KAC/B,CAAC,CAAC;AACL,CAAC,CAAC;AAEF,eAAe,OAAO,CAAC"}

package/dist/index.d.ts

@@ -0,0 +1,42 @@
+/**
+ * @aight/utils — OpenClaw gateway plugin
+ *
+ * Push notifications, Today items, config RPC, and agent bootstrap for the Aight app.
+ */
+import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
+declare const aightPlugin: {
+    id: string;
+    name: string;
+    description: string;
+    configSchema: {
+        parse(value: unknown): {
+            push: {
+                mode: any;
+                relayUrl: any;
+                relaySecret: any;
+            };
+            today: {
+                enabled: any;
+            };
+        };
+        uiHints: {
+            "push.mode": {
+                label: string;
+                help: string;
+            };
+            "push.relayUrl": {
+                label: string;
+                placeholder: string;
+            };
+            "push.relaySecret": {
+                label: string;
+                sensitive: boolean;
+            };
+            "today.enabled": {
+                label: string;
+            };
+        };
+    };
+    register(api: OpenClawPluginApi): void;
+};
+export default aightPlugin;