4todo

---
name: 4todo
description: Manage 4todo (4to.do) from chat. Capture tasks, prioritize with the Eisenhower Matrix, reorder, complete, and manage recurring tasks across workspaces.
---

# 4todo
[4to.do](https://4to.do) Eisenhower Matrix To‑Do List

## Goal

- Use `curl` to call the 4todo API (`https://4to.do/api/v0`) to manage:
  - workspaces
  - todos
  - recurring todos
- Store the token in a way that is injectable but not leak-prone (prefer OpenClaw per-run env injection; do not paste secrets into prompts, logs, or repo files).

## Required Environment Variable

- `FOURTODO_API_TOKEN`: your 4todo API token (Bearer token)
- If missing, ask the user to set it via OpenClaw config (do not ask them to paste the token into chat).

## Runtime Requirement

- `curl` must be available on `PATH` (and inside the sandbox container, if the agent is sandboxed).

## User-facing output rules (important)

- Be non-technical by default. Focus on outcomes, not implementation.
  - Avoid mentioning: curl, endpoints, headers, API mechanics, JSON payloads, config patches.
  - Mention technical details only when debugging or if the user explicitly asks “how does it work?”.
- Do not print internal IDs by default:
  - Do **not** show `ws_...`, `todo_...`, `rec_todo_...` unless the user asks.
  - Refer to workspaces and tasks by **name**.
  - If disambiguation is needed (duplicate names), ask a clarifying question and present a short numbered list of names; only offer IDs if the user requests them.
- Quadrants:
  - In chat, prefer plain language: “urgent & important”, “important (not urgent)”, “urgent (not important)”, “neither”.
  - Use `IU | IN | NU | NN` internally for API calls. Only show codes if the user uses codes first or explicitly asks.

### Examples (preferred)

Workspaces:

```
Your workspaces:
1) Haoya (default)
2) 4todo
3) Echopark
```

Todos (summary):

```
Urgent & important:
1) UK company dissolution
2) Hetzner monthly payment (recurring, monthly)

Important (not urgent):
1