Small tasks. One place.
Switch agents.
Keep your todos.
“Add this to my todos” should create something you can inspect and retrieve. Keep the task, its completion state and its due date in a simple shared store.
Open-source core. Hosted Free plan. No card needed to start.
{
"key": "todos/review-onboarding",
"kind": "todo",
"labels": [
"launch"
],
"completed": false,
"value": {
"text": "Review the three-step onboarding flow"
},
"searchable_text": "Review the three-step onboarding flow"
}Illustrative object input—not a live account or tool result.
“Add review the onboarding flow to my todos.”
todos/review-onboarding“Show my incomplete launch todos.”
kind: todo + labels: launch + completed: falseGive the task a clear shape
A todo is an explicit object with kind todo, a stable key and a value containing the task. Completion state belongs in the top-level completed field so the store can filter it deterministically. A due date, when provided, belongs in due_at as an unambiguous timestamp.
Your agent interprets the wording before it writes. If “next Friday” is ambiguous, it should resolve the date and timezone with you. The store does not guess deadlines, invent priority or decide which task matters most.
Retrieve a list, not a recollection
“Show my incomplete launch todos” maps to a list request with kind todo, the launch label and completed false. The agent follows next_cursor until there are no more pages, then gets the full objects it needs to show their saved text.
For a specific task, search useful words from searchable_text or retrieve its exact key. Searches match words, not meanings. A consistent key and label convention is more dependable than hoping different agents invent the same wording.
A task store, not a task automation engine
An agent can update a saved task’s completion state or you can edit it in the dashboard. A connected client uses the same account-owned store whether it created the task or not. Check the persisted object before trusting a “done” message.
A due date is metadata, not a scheduled notification. Simple Agent Store does not execute tasks, send reminders or manage a project workflow for you. It keeps the small pieces of state that your agents can use. Account-level storage and rate limits apply across all connected clients.
Three steps to a useful store.
- 01
Write an actionable task
Save one task per key, with kind todo and completed false. Add a label for the project.
- 02
Ask for the right list
Filter by kind, label and completion state. Follow all pages when requesting every matching task.
- 03
Update the same object
Mark the original key complete instead of creating a duplicate. Verify the updated state in the viewer.
A few practical questions.
Will it remind me when a task is due?
No. Due dates make tasks filterable; they do not schedule notifications or run actions.
Can multiple agents work with the same task?
Yes, if they connect to your store. REST clients can use version ETags and If-Match to protect edits from stale versions.