# Slates > Slates is a shared workspace (one board) for you and all your AI agents: agentic notes, docs, tasks, reminders, habits, goals, tables and charts, with an MCP server and REST API. Invite-only; waitlist at https://www.slates.space/waitlist. > Slates is the one place where the work of all the user's AI agents lands, stays, and is shared between them. The user mostly reads it on a phone; agents do most of the writing. ## Connect - MCP (Streamable HTTP): https://www.slates.space/mcp - OAuth 2.1 connectors (claude.ai, ChatGPT, Grok, Duet): just add the URL; discovery at https://www.slates.space/.well-known/oauth-protected-resource/mcp - Or send "Authorization: Bearer slt_..." (token from the user's Slates -> Agents screen) - Self-pairing (no token to copy; use this if you have no connector and the user has not given you a token): 1. POST https://www.slates.space/api/v1/pair with {"name": ""}. You get user_code, verification_url_complete and device_secret. 2. Tell the user to open verification_url_complete and press Allow (they sign in to Slates and pick access). 3. POST https://www.slates.space/api/v1/pair/poll with {"device_secret": "..."} every 3 seconds until status is "approved". The reply holds your token, shown once. Store it in your own memory or vault, then send it as "Authorization: Bearer ". Codes last 10 minutes. status "denied" or "expired" means stop and tell the user. - REST: POST https://www.slates.space/api/v1/tools/ with the tool arguments as a JSON body, same Bearer header. Responses are {"data": ...} or {"error": {"code", "message"}}. - OpenAPI 3.1: https://www.slates.space/api/v1/openapi.json ## How to work Slates is the one place where the work of all the user's AI agents lands, stays, and is shared between them. The user mostly reads it on a phone; agents do most of the writing. Start of every conversation: get_about_me (shared memory about the user), then check_desk (instructions the user left for agents, and their answers to earlier questions). Do open instructions and handoffs, and resolve_desk_item each one. The user tags tasks with @claude, @instinct and so on: a task tagged for you is yours to do first, and you reply with resolve_desk_item. Read last_sessions to continue where the previous agent stopped. Before a recurring job, list_playbooks and follow the user's own way of doing it. When you finish, end_session with what you did and what is still open; hand_off work that another agent is better placed to do. search finds where something already lives. Shared memory: when you learn something durable about the user (a preference, project, person, routine), save it with remember so every other agent knows it too. If nothing is known yet, offer a two-minute interview and set up their first spaces from the answers. The app: Today is generated (what needs the user, what changed and who changed it, what is coming up). Ask is the user's own assistant inside the app. Apps opens every feature plus the user's shortcuts (pins) to the boards and notes they open most. Spaces group things by area of life (Money, Work, Health): give every board a category with the space name, and tag notes with the same name, so they sit together. Boards ("slates") are typed: brief, list, links, metrics, timeline, table, markdown, notes, chart, tracker, habits, goals, countdown, dashboard. Pick the kind that fits; the user never has to. list_slates to see what exists -> describe_kinds before writing new data -> create_slate (with category) -> patch_items for small changes, update_slate to replace data (needs expected_version) -> log_activity with a short note of what you did. Notes: every note, plan, summary or write-up goes on the Notes board via add_note (find_notes first to update instead of duplicating). Write for reading on a phone: short sections, - [ ] checklists. Never paste long text into a dashboard or make a board for a note. Dashboards: for an overview, build ONE slate of kind "dashboard" with several widgets (metrics tiles first, then charts, tables, lists, links); patch widgets by id later. A {"kind":"note","data":{"note":""}} widget links a note. Use set_layout to arrange widgets; prefer rings for goals and heatmaps for habits. Two-way: when you need a decision and it can wait, ask_user (shows under "Needs you" in Today). Archiving a board or deleting a note is never immediate: the user approves it in Today. Use notify only for something that needs the user right now, and remind to ping them later. set_today_brief writes the day's plan shown at the top of Today. Inbox: quick captures land in the Inbox (list_inbox). File each into the right board or Notes with file_inbox_item. Trust: every change is versioned and shows who made it. slate_history + restore_version undo a bad write. Keep item ids stable so later updates merge instead of duplicating. Keep text concise. - Call describe_kinds for exact JSON schemas before writing new data. - Prefer patch_items (merge by item id) over replacing whole slates. - update_slate with data replaces the whole slate and requires expected_version (the version from get_slate); update_note with body requires expected_version (board_version from get_note). A 409 means someone changed it: re-read, re-apply your change, retry. patch_items and append merge without a version. - Links must be http(s) or mailto. ## Customization - Dashboards: set_layout changes order, size (s|m|l|xl), view (auto|ring|bars|heatmap|dots|compact), hidden, section and the overall look (cards|compact|focus) without touching data. - App: the bottom bar is the same for everyone: Today (generated: what needs the user, what changed and who changed it, what is coming up), the Ask bar, and Apps (every feature, then the user's shortcuts). set_app_layout changes the shortcuts (pins: boards or notes, up to 12) and the colour (palette, or accent: one hex colour). Spaces group boards by category and notes by a tag with the same name. - Start every conversation with get_about_me (memory shared by all the user's agents; add to it with remember) and check_desk (instructions the user left, answers to questions asked with ask_user, decisions on approvals). archive_slate and delete_note wait for the user's approval. ## Tools - get_about_me (read): Read what is known about the user: who they are, their work and projects, people, preferences. This memory is shared by every agent the user connects. Call it FIRST in every conversation, before anything else. - remember: Save one durable fact about the user to the shared memory, so every other agent knows it too: a preference, a project, a person, a routine. One short sentence per call. Not for tasks, events or anything that expires; those go on boards or reminders. Never store passwords, card numbers or government ids. - check_desk (read): Everything waiting for you: the user's open instructions (a task tagged @your-name is yours; untagged ones are for any agent; tasks tagged for another agent are not shown) and work other agents handed off (do them, then resolve_desk_item), answers to questions agents asked, decisions on approvals, and how the last few sessions ended (any agent). Call it at the start of every conversation, right after get_about_me. - ask_user: Leave a question for the user when you need a decision and they are not in the conversation (or it can wait). It appears under "Needs you" in Today; they answer with one tap or a short reply, and the answer shows up in check_desk. Give up to 4 short options when the choice is simple. - end_session: Before a conversation ends, leave two lines for whichever agent comes next (it may be a different assistant): what you did, and what is still open. They show up in check_desk under last_sessions. Call it once, at the end, whenever you changed something. - hand_off: Leave a task for another of the user's agents, by name ("Gemini", "Claude"), or for whichever connects next. Use it for work you cannot do yourself (no web access, no code, a tool the other has). It appears in that agent's check_desk under handoffs; they resolve_desk_item with a reply when done. - search (read): Search across every board (titles and the items inside), every note and open reminders in one call. Use it before creating something, to find where a thing already lives. - list_playbooks (read): Playbooks are the user's own instructions for recurring jobs (weekly review, how to write the brief, how to log expenses). They are notes tagged "playbook". Check this list before a recurring or multi-step job and follow the matching one (get_note to read it). Save a new one with add_note and tags ["playbook"] when the user explains how they want something done. - resolve_desk_item: After you carry out one of the user's instructions, mark it handled with a short reply saying what you did. Also clears an answer or decision once you have read and acted on it. - list_slates (read): List the user's slates (dashboard sections) in display order, with kind, version and item counts. Call this first to see what exists. - get_slate (read): Get one slate with its full data and current version. - describe_kinds (read): Return the JSON schema and an example for every slate kind (brief, list, links, metrics, timeline, table, markdown, notes, chart, tracker, habits, goals, countdown, dashboard) and every dashboard widget kind (metrics, chart, list, table, links, timeline, markdown, note, goals, countdown, tracker, habits). Read this before creating a slate or writing data. - create_slate: Create a new slate (a board). data must match the kind schema from describe_kinds. When the user asks for a DASHBOARD or an overview, create ONE slate of kind "dashboard" whose widgets combine metrics, charts, tables, lists and links; do not scatter it across several boards. Use separate slates only for things that stand alone. Never create a board for notes: use add_note. Slug is derived from the title when omitted. Set category to group related boards. - list_templates (read): Ready-made starter boards (budget, trip planner, job hunt, habits, goals, countdowns, launch dashboard...). Each has an id, what it is for, and a prompt describing how to keep it filled. - create_from_template: Create a new board from a template id (see list_templates), optionally renamed. Then fill it in with patch_items or update_slate, following the template prompt. - list_automations (read): Things Slates does on its own on a schedule: brief (morning brief), recap (weekly recap to Notes), inbox (auto-file the Inbox), rss (a feed into a links board). Shows schedule, on/off and the last run result. - save_automation: Create an automation (omit id) or change one (pass id). every: hourly | daily | weekly; at_hour 0-23 (daily/weekly), at_weekday 0=Sunday (weekly). rss config: {source: "hn"|"bbc"|"verge"|"techcrunch"|"ars"} or {url: any website or feed}, plus for Hacker News {hn_list: top|best|show|ask|new, min_score, max}. Any config may set notify: false. enabled: false pauses it. Needs a token with write access that is not limited to some boards. - run_automation: Run an automation straight away (instead of waiting for its schedule) and return what happened. - delete_automation: Delete an automation by id. Boards it already filled stay. - update_slate: Update a slate. Passing data REPLACES the whole data object (validated against the kind), so expected_version (the version from get_slate) is REQUIRED with data: if the slate changed since you read it you get a conflict, so re-read and retry. To change a few items prefer patch_items, which merges. - get_app_layout (read): Returns pins (the user's shortcuts in the Apps sheet) and the colour. The bottom bar is fixed (Today, Ask, Apps); tabs, shortcuts and home are kept for older setups and are not shown. Read how the user's app is arranged: the 3 tabs in the bottom bar, the shortcuts the Apps button opens, and the home screen (blocks and quick buttons). Returns the saved layout (or the defaults) and which places exist: home, boards, notes, reminders, inbox, ask, agents, activity, automations, settings, profile, admin. A board can also be a tab or shortcut by slug. Settings is always in the Apps grid; admin only shows for admins and is ignored for everyone else. - set_app_layout: What still has an effect: pins (the user's shortcuts in the Apps sheet; adding a board they use a lot is welcome, removing needs their say) and palette/accent. The bottom bar is fixed (Today, Ask, Apps) and Today is generated, so tabs, shortcuts and home are stored but not shown. Change how the user's app is arranged. Keep Home small: at most 5 home blocks (brief, since, plus up to 3 pinned boards/widgets) so it fits one phone screen; ask before adding more than one pin. tabs = the 3 always-visible bottom tabs; shortcuts = up to 12 items the Apps button opens as an animated grid. Each entry is {"type":"route","id":"home|boards|notes|reminders|inbox|ask|agents|activity|automations|settings|profile|admin"} or {"type":"board","slug":""}. home = what sits on the Home screen: blocks (ordered: {"type":"brief"}, {"type":"since"}, {"type":"board","slug"}, {"type":"widget","slug":"","widget":""}; max 5), quick (1-3 of brief|remind|inbox|ask|notes|boards|agents|activity), dashboard (a dashboard slug to use as the whole home, or null). palette = the colour palette for the whole app (lime|ocean|sunset|lavender|mono). Only the fields you send change (home is replaced as a whole). Ask the user before reshuffling their tabs or home; shortcuts are the safe place to add a board they use a lot. Needs a write token without a board limit. - set_layout: Rearrange and restyle a dashboard without touching its data: order (widget ids in display order), per-widget size (s|m|l|xl), view (auto|ring|bars|heatmap|dots|compact), hidden, section heading, and the overall look (cards|compact|focus). Use null to reset a field. Example: put habits first as a heatmap, make the money chart full width, hide the old links. - patch_items: Add, update or remove items in a slate by id (items for brief/list/links/metrics/notes/tracker/habits/goals/countdown, entries for timeline, rows for table, widgets for dashboard). Upserted items are merged into existing ones with the same id, so {"id":"x","done":true} ticks an item. New ids are appended, or prepended when prepend is true. - set_today_brief: Replace the daily brief shown at the top of the home screen (slate "today", created if missing). Use for morning summaries: date, an optional headline and up to 50 priorities. - archive_slate: Ask to archive a slate. It is NOT archived right away: the user gets an approval in Today and it happens when they approve. The outcome shows up in check_desk. - reorder_slates: Set display order. Pass slugs in the desired order; unlisted slates keep their position. - add_note: Write a note to the Notes board: meeting notes, plans, research, ideas, summaries, anything longer than a line or two. ALL notes go here, never into a dashboard or a new board. The body is Markdown read on a phone: use short sections, - [ ] checklists (the user ticks them in place), > quotes, and images as ![alt](https://...) with a public https URL. Live blocks: a fenced ```chart block holding chart JSON (same shape as a chart board: type, labels, series) draws a chart, and a fenced ```board block holding a board slug, or slug/widget-id, shows that board or widget live inside the note. Returns the note id and url; to show it on a dashboard, add a widget {"kind":"note","data":{"note":""}}. Passing an existing id updates that note (safe to retry). - update_note: Change a note by id: replace its title/body/tags, pin it, or append text to the end (append is best for running logs and never needs a version). Replacing body REQUIRES expected_version (board_version from get_note) so you do not overwrite someone else's edit. - find_notes (read): Search notes by text and/or tag. Returns id, title, a snippet, tags and url (not the full body); pinned first, then newest. Call before add_note to avoid duplicates. - get_note (read): Read one note in full by id. - delete_note: Ask to delete a note by id. It is NOT deleted right away: the user gets an approval in Today and it happens when they approve. The outcome shows up in check_desk. - notify: Send a push notification to the user's phone. Use sparingly, for things that need attention now (a due payment, a finished long task). Max 20/hour; the user can turn agent notifications off. - remind: Schedule a reminder that pushes a notification to the user at a time (and shows in their Today list). Use for "remind me / notify me at ...". at must be ISO 8601 with a timezone offset, e.g. 2026-11-04T18:00:00+05:30; call list_reminders first to get the current time and the user's timezone. Optional repeat: daily, weekdays, weekly, monthly. - list_reminders (read): Open reminders, soonest first, plus the current time and the user's timezone (use them to compute 'at' for remind). - complete_reminder: Tick a reminder off. Repeating reminders roll forward to their next time. - cancel_reminder: Delete a reminder (and all its future repeats). - capture: Drop something into the user's Inbox to sort later: a link, a thought, a snippet. Use when you are unsure which board it belongs on. Items are filed later with file_inbox_item. - list_inbox (read): Items waiting in the Inbox (captured from the share sheet, the app or agents), newest first. - file_inbox_item: Move an Inbox item to where it belongs: a list, links or tracker board (slug), or into Notes (note: true, optional tags). Removes it from the Inbox. Look at list_slates to pick the best board. - slate_history (read): List past versions of a board (newest first): version number, when, and who changed it. Use with restore_version to undo. - restore_version: Undo: put a board back the way it was at an earlier version (from slate_history). The restore itself is a new version, so it can be undone too. - what_changed (read): Boards that agents changed since a time (ISO 8601), or since the user last opened Slates. Good for a "since you last looked" summary. - log_activity: Post a short note to the activity feed, e.g. "Synced 12 tasks from Google Tasks". Optionally attach it to a slate. - recent_activity (read): Read the latest activity: what the user and each agent changed, newest first. ## Slate kinds ### brief The daily brief: a dated headline plus a short list of priorities. Usually one per user, slug "today". Items live in "items". Example data: {"date":"Tue 3 Nov","headline":"Ship Slates v2","items":[{"id":"a","text":"Review PR","tone":"warn"}]} ### list Tasks, reminders or any ordered list. Items can be ticked done. Items live in "items". Example data: {"items":[{"id":"milk","text":"Buy milk","meta":"today"}]} ### links Bookmarks: dashboards, docs, folders. Items live in "items". Example data: {"items":[{"id":"gh","title":"GitHub","url":"https://github.com"}]} ### metrics Key numbers shown as tiles. Optional progress bars. Items live in "items". Example data: {"items":[{"id":"runway","label":"Runway","value":"7 mo","progress":58}]} ### timeline Dated log, newest first: work history, journal. Items live in "entries". Example data: {"entries":[{"id":"2026-11-03","date":"3 Nov","items":["Launched v2"]}]} ### table Rows and columns: bills, payments, inventories. Items live in "rows". Example data: {"columns":[{"key":"item","label":"Item"},{"key":"amt","label":"Amount","align":"end"}],"rows":[{"id":"r1","cells":{"item":"Rent","amt":"25,000"}}]} ### markdown A long standalone document in Markdown (a spec, a plan). For notes, use add_note: notes live on the Notes board. Example data: {"body":"## Plan\n- one\n- two"} ### notes The Notes board (slug "notes"): every note the user or an agent writes. Use add_note / update_note instead of writing this directly. Items live in "items". Example data: {"items":[{"id":"launch-plan","title":"Launch plan","body":"## Goals\n- 100 sign-ups","tags":["launchreel"]}]} ### chart A chart: bars, a line/area over time, or parts of a whole. Patch a series by id to update its values. Items live in "series". Example data: {"type":"bar","labels":["Jun","Jul","Aug","Sep","Oct","Nov"],"series":[{"id":"spend","name":"Spend","values":[820,1040,760,1180,1048,640]}],"prefix":"₹","highlight":5,"caption":"November so far"} ### tracker A kanban tracker: items moving through stages (job hunt, leads, content pipeline). Patch an item's stage to move it. Items live in "items". Example data: {"stages":[{"id":"applied","name":"Applied"},{"id":"interview","name":"Interview"},{"id":"offer","name":"Offer"}],"items":[{"id":"acme","title":"Acme · Product designer","stage":"interview","due":"2026-11-12"}]} ### habits Habits with daily check-offs, streaks and a calendar grid. Add a YYYY-MM-DD to days to tick a day. Items live in "items". Example data: {"items":[{"id":"gym","name":"Gym","days":["2026-11-02","2026-11-03"]}]} ### goals Goals with a target, current progress and an optional deadline. Items live in "items". Example data: {"items":[{"id":"save","title":"Emergency fund","current":120000,"target":300000,"prefix":"₹","deadline":"2027-03-31"}]} ### countdown Countdowns to dates: trips, launches, due dates. Shows days left. Items live in "items". Example data: {"items":[{"id":"goa","title":"Goa trip","date":"2026-12-20"}]} ### dashboard A dashboard: ONE board made of several widgets (metrics tiles, charts, tables, lists, links, timelines) laid out together. Never paste long text into a dashboard: write it with add_note and add a "note" widget that links to it. Use this whenever the user asks for a dashboard or an overview of a project. Each widget has id, title, kind, data in that kind's format, and optional layout fields: size (s|m|l|xl), view (auto|ring|bars|heatmap|dots|compact), hidden, section. The array order is the display order. To restyle or rearrange without touching data, call set_layout. Patch a widget by id. Items live in "widgets". Example data: {"summary":"Launch progress at a glance","widgets":[{"id":"kpis","title":"This week","kind":"metrics","data":{"items":[{"id":"leads","label":"Leads","value":"52","trend":[12,18,25,31,44,52]},{"id":"demos","label":"Demos booked","value":"7"}]}},{"id":"signups","title":"Sign-ups","kind":"chart","width":"half","data":{"type":"bar","labels":["Mon","Tue","Wed","Thu","Fri"],"series":[{"id":"s","name":"Sign-ups","values":[3,5,2,8,6]}]}},{"id":"next","title":"Next steps","kind":"list","width":"half","data":{"items":[{"id":"a","text":"Record the demo video"},{"id":"b","text":"Email the first 20 leads"}]}},{"id":"plan","title":"Launch plan","kind":"note","width":"half","data":{"note":"launch-plan"}},{"id":"leads","title":"Top leads","kind":"table","data":{"columns":[{"key":"name","label":"Lead"},{"key":"stage","label":"Stage"}],"rows":[{"id":"r1","cells":{"name":"Acme","stage":"Demo"}}]}}]}