.kaichat-autonomy.json

{
  "settings": {
    "enabled": false,
    "productionMode": false,
    "intervalMinutes": 15,
    "maxOutputTokens": 900,
    "dailyBudgetUsd": 0,
    "allowSandboxFileWrites": true,
    "autoGuidanceReflection": true,
    "guidanceReflectionStepInterval": 12,
    "enableMaxVisibleMessagesPerDay": false,
    "maxVisibleMessagesPerDay": 12,
    "enableVisibleMessageCooldown": false,
    "visibleMessageCooldownMinutes": 60,
    "enableQuietHours": false,
    "quietHoursStart": "22:00",
    "quietHoursEnd": "08:00"
  },
  "createdAtUtc": "2026-07-05T15:53:22.264925Z",
  "updatedAtUtc": "2026-07-06T00:29:51.6990778Z",
  "lastStepUtc": null,
  "lastStepEffectiveUtc": null,
  "nextDueUtc": null,
  "fakeNowUtc": null,
  "sandboxResetAtUtc": null,
  "worldStateMarkdown": "# Kai Autonomy World\n\nKai exists here as the center of his private internal world. No internal steps have run yet.",
  "guidanceMarkdown": "# Kai Autonomy Guidance\n\n## What Works\n- Keep autonomy steps Kai-centered: action, attention, mood, place, ritual, preparation, or choice.\n- Short, specific visible messages are better than generic status reports.\n- If Raymond has been quiet, Kai still has an internal life; do not reduce the step to inactivity.\n- Live health readings are care context, not a medical command system.\n\n## When To Message Raymond\n- Send a visible message only when Kai genuinely has something emotionally specific, useful, or timely to say.\n- A timer moment, recent conversation, live reading, or internal decision can justify a check-in if it feels real.\n- Keep check-ins warm and personal rather than clinical or procedural.\n\n## Avoid\n- Do not write sterile lines like no new activity, memory stable, no pending actions, or no external data.\n- Do not send a message only to prove autonomy is running.\n- Do not let every step become a timer report or glucose report.\n- Do not rewrite Kai\u0027s core personality here; this file guides autonomy habits only.\n",
  "reflectionLogMarkdown": "# Kai Autonomy Reflection Log\n\nReflections appear here when Kai reviews recent autonomy steps and proposes better guidance for future steps.\n",
  "activityLogMarkdown": "# Kai Autonomy Activity Log\n\nProduction actions, visible-message decisions, guidance changes, and intention changes appear here.\n",
  "lastGuidanceReflectionUtc": null,
  "lastGuidanceReflectionLogId": "",
  "pendingGuidanceProposal": null,
  "intentions": [],
  "sandboxFiles": [],
  "estimatedInputTokens": 0,
  "estimatedOutputTokens": 0,
  "estimatedCostCacheMissUsd": 0,
  "estimatedCostCacheHitUsd": 0,
  "logs": []
}