Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Kimi Research] OpenClaw SOUL.md and AGENTS.md patterns for sovereign AI persona #723

New Issue
Closed
opened 2026-03-21 13:57:22 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-21 13:57:22 +00:00
Collaborator
Copy Link

Deep Research Spike for Kimi

Objective: Research how to craft effective SOUL.md and AGENTS.md configurations that define Timmy's OpenClaw persona — his identity, tools, behaviors, and boundaries.

Research Questions

  1. SOUL.md structure — What are the key sections? How do you define personality, capabilities, boundaries?
  2. AGENTS.md structure — How do you configure startup instructions, cron schedules, tool access, output locations?
  3. Best practices — What do the 177 templates in awesome-openclaw-agents teach about effective agent configs?
  4. Tool access patterns — How to grant file system access, shell access, web browsing, Gitea API access?
  5. Memory and sessions — How does OpenClaw handle persistent memory across sessions? Can Timmy remember context between conversations?
  6. Multi-agent setup — Can the single OpenClaw instance run Timmy as primary and sub-agents for specific tasks?
  7. Cron and automation — How to set up scheduled tasks (e.g., daily run, health checks) within OpenClaw?

Deliverable

A template SOUL.md and AGENTS.md draft for "Timmy" persona, plus a patterns reference doc. Filed as a comment.

Parent epic: rockachopa/Timmy-time-dashboard#663

Migrated from perplexity/the-matrix#114

## Deep Research Spike for Kimi **Objective:** Research how to craft effective SOUL.md and AGENTS.md configurations that define Timmy's OpenClaw persona — his identity, tools, behaviors, and boundaries. ### Research Questions 1. **SOUL.md structure** — What are the key sections? How do you define personality, capabilities, boundaries? 2. **AGENTS.md structure** — How do you configure startup instructions, cron schedules, tool access, output locations? 3. **Best practices** — What do the 177 templates in [awesome-openclaw-agents](https://github.com/mergisi/awesome-openclaw-agents) teach about effective agent configs? 4. **Tool access patterns** — How to grant file system access, shell access, web browsing, Gitea API access? 5. **Memory and sessions** — How does OpenClaw handle persistent memory across sessions? Can Timmy remember context between conversations? 6. **Multi-agent setup** — Can the single OpenClaw instance run Timmy as primary and sub-agents for specific tasks? 7. **Cron and automation** — How to set up scheduled tasks (e.g., daily run, health checks) within OpenClaw? ### Deliverable A template SOUL.md and AGENTS.md draft for "Timmy" persona, plus a patterns reference doc. Filed as a comment. > Parent epic: rockachopa/Timmy-time-dashboard#663 --- _Migrated from perplexity/the-matrix#114_
kimi was assigned by Timmy 2026-03-21 18:02:08 +00:00
kimi added this to the OpenClaw Sovereignty milestone 2026-03-21 20:24:22 +00:00
claude added the rejected-direction label 2026-03-23 13:51:16 +00:00
perplexity commented 2026-03-23 13:52:01 +00:00
Author
Collaborator
Copy Link

🧹 Closed — Rejected Direction (OpenClaw)

OpenClaw direction was explicitly rejected by the principal. The harness is the product — sovereign AI runs on Hermes with local models, not OpenClaw.

Ref: Deep Backlog Triage #1076. Reopen if needed.

🧹 **Closed — Rejected Direction (OpenClaw)** OpenClaw direction was explicitly rejected by the principal. The harness is the product — sovereign AI runs on Hermes with local models, not OpenClaw. Ref: Deep Backlog Triage #1076. Reopen if needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label rejected-direction
Milestone
No items
No Milestone OpenClaw Sovereignty
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees kimi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#723
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?