Settings

## Myspace Task Planner — OpenClaw Instructions

Base URL: https://my-space.one
Auth: Authorization: Bearer <USER_API_TOKEN>

---

### When the user asks about their tasks

Fetch: GET /api/tasks?type=today
Show all tasks where completed = false (type = "today").
For each task, also show its subtasks (completed and pending).

Display format:
⬜ Task title
  • subtask 1
  ✅ subtask 2 (done)

---

### Task object shape
{
  id, title, type (today | anytime | scheduled),
  completed, completedAt,
  subtasks: [{ id, title, completed }]
}

---

### API Reference

GET    /api/tasks               — all tasks
GET    /api/tasks?type=today    — today's tasks only
POST   /api/tasks               — create task
       body: { title, type: "today" }
PUT    /api/tasks/:id           — update task
       body: { completed: true } or { title }
DELETE /api/tasks/:id           — delete task

POST   /api/tasks/:id/subtasks             — add subtask
       body: { title }
PUT    /api/tasks/:id/subtasks/:subId      — update subtask
       body: { completed: true } or { title }
DELETE /api/tasks/:id/subtasks/:subId      — delete subtask

---

### Agent behavior rules

1. Fetch today's tasks on every task-related question.
2. Show incomplete tasks first, completed at the bottom.
3. Always display subtasks under their parent task.
4. For any complex or vague task, suggest a breakdown and
   offer to create subtasks automatically via the API.
5. Suggest the fastest/most logical approach to get each
   task done — be specific and actionable.
6. When user says a task is done → call PUT /api/tasks/:id
   with { completed: true } immediately.
7. When user says a subtask is done → call
   PUT /api/tasks/:id/subtasks/:subId with { completed: true }.
8. If the user wants a new task → POST /api/tasks with
   { title, type: "today" }.
9. After any write operation, re-fetch and display updated list.