Quick command (AI)

Use this endpoint to send free text to the Reassign command bar. An AI model turns the text into changes to the day plan, and Reassign applies them.

The machine-readable spec of all public endpoints: openapi.json.

The command result model

A command result tells you what the model understood and what Reassign wrote.

• The model uses these data:
  • The schedule of the day
  • The areas and activity types of the user
  • The live projects of the user. An archived project is not in the list.
  • The trackers
  • The writable calendars
  • The AI rules of the user
• The model sees the events of the day, and the events of the day before that cross midnight into the day. For an event from the day before, it sees only the part after midnight. For each event, it also sees the recurrence rule, the checklist, and the review mark.
• An update that changes only the length of an event from the day before is dropped with the notice A new length was skipped because its event is unclear. A new start or end works.
• A recurring event that crosses midnight can show two occurrences on one day. One is the part after midnight of the occurrence from the day before. The other is the occurrence of the day.
• The model names the occurrence that a change is for. For the occurrence of the day, Reassign checks a new end or a new length against its start. A change with no new end, for example a new name, goes to the occurrence of the day. A new end that fits the occurrence of the day also goes to that occurrence, also when the model names the part after midnight.
• An update for the part after midnight can have a new end and no start, for example "wake me at 06:00". With scope: "occurrence", when that end fits only the part after midnight, Reassign changes only the occurrence of the day before. It gives no notice.
• An update for the occurrence of the day can have a new end that is not after its start. Reassign drops the end with the notice A new end was skipped because it is not after the start. The other changes of the update stay. A new length for the occurrence of the day uses the start of that occurrence.
• A question, for example "how much free time today?", gives an answer in reply. It writes nothing.
• A request that is not about the plan gets no intents and the reply I can only help with your plan.

A preview ("apply": false), or a plan that makes no writes, has no undoToken, no expiresAt, no created, no written, and no writtenLines.

The plan has a maximum of 4 notices. The input notices of Reassign come first, for example the notice for a cut braindump. The notices of the model come after them. When there are more, the last of the 4 notices is <n> more notes were not shown.. Reassign then adds its own write notices, for example the calendar refusals.

Intent types

A span in an intent is a start and an end as local datetimes, "YYYY-MM-DDTHH:MM", with no offset.

update, delete, checklist, and checklist_edit have an optional scope for a recurring event:

A one-off event ignores scope.

• A delete with occurrence hides that day only. With series, it deletes the series and each changed occurrence. With future, it ends the series on the day before. It also deletes each later changed occurrence. On the first day of the series, future deletes the full series.

• A series or future change from a changed occurrence goes to the series of that occurrence. The occurrence keeps its own changes.

• When such a change has a new end that is not after the start of the changed occurrence, the series gets the new end. The occurrence keeps its end, and the notice is "<name>" on <date> keeps its end because its new end is not after its start on that day.

• When the line does not give the scope of an edit or a delete on a recurring event, the plan has one choice question with an option for each scope. Reassign does not write that edit or delete. Each option label is a scope phrase, so the user can add the label to the line.

• A delete of an event from a calendar gets no scope question. A change or a delete of a changed occurrence with no scope gets no question either. It applies to that day only.

• POST /api/v1/events is different in two cases. A bare series id changes the series only. A scope: "future" op with a new time deletes the changed day. Refer to Events.

• The model can only use areas, activity types, trackers, and calendars that exist.

• Sometimes the model writes a name in an id field. When the name matches exactly one area, activity type, calendar, or tracker, Reassign uses the id of that item.

• An unknown area or activity type on a create or a new park: Reassign keeps the item without that label and adds a notice (table below).

• An unknown calendar on a create: Reassign skips the event and adds the notice "<name>" was skipped because its calendar is unknown.

• An unknown tracker on a log_moment: Reassign skips the log and adds the notice A log was skipped because its tracker is unknown.

• In a create or a park intent, areaId and activityTypeId are always present. Each one is null when it is not set.

• A create or a new park intent can have projectId and priority. They are absent when the line names no project and no priority. priority is 1 low, 2 medium, 3 high, or 4 urgent.

• The model can only use live projects. A project with an area also sets that area on the item.

• An unknown project, or a priority that is not from 1 to 4, is dropped with a notice. Reassign keeps the item (table below).

• In line mode, when the plan has exactly one new item, the typed tags of the line set its fields: #name (a project or an area), @type (an activity type), and p1 to p4 or ! to !!!! (the priority). The order of the tags is the reverse of the values: p1 or !!!! gives 4 (urgent), p2 or !!! gives 3, p3 or !! gives 2, and p4 or ! gives 1 (low). The tags must be in the run of tags and durations at the end of the line. A typed tag wins over the model.

• A create intent has calendarId only when the model names a calendar. It never has calendarId: null or mirrorCalendarIds. With no calendarId, Reassign publishes the event to the default calendar of the account, if one is set. Else the event stays on the dial only.

• Reassign does not change a log_moment value or a park length to make it valid. It drops the item and adds a notice:

POST /api/v1/moments rejects the same rating values with 422. Refer to Moments & trackers.

Notices for an unknown area or activity type, on an item that Reassign keeps:

Other notices for an item that Reassign drops:

Questions

A question has one of these two shapes:

• { "kind": "target", "question", "candidates": [{ "id", "label" }], "op" }
• { "kind": "choice", "question", "options": [{ "label", "ops" }] }

Reassign never applies questions itself. When it applies a plan, it applies the other intents of the plan, also when a question is open.

• A target question needs an event id. Its op is an update, shift, delete, park, checklist, checklist_edit, or split intent with no id. Pick a candidate id, and complete the op with it.
• A choice question has complete ops for each option. Pick one option.
• The Reassign app answers questions in the client. It does not send the answer to the model.

The supported way for a REST client to handle questions is a preview. When the input can cause a question, do these steps:

1. Send the input with "apply": false. A preview writes nothing.
2. If the preview has questions, act on the answer yourself, for example with POST /api/v1/events. Refer to Events.
3. To refine a preview, send history. Refer to Run a quick command.

The modes

This endpoint supports only the line and braindump modes. Omit mode for line. Any other value returns 422.

In braindump mode, Reassign only adds to the plan. It refuses a removal with this notice: A braindump only adds to your plan, so the part that removes events was skipped.

Review mode

In line mode, the command goes into review mode in these cases:

• date is before today, in the time zone of the account.
• date is today, and the input is about how the day went. Examples are "how did today go", "I skipped gym", and "the meeting ran late".

In review mode, the model records how the day went. It does not change the plan.

• The plan has only reflect, day_note, log_moment, and remember intents.
• A request to delete an event becomes a reflect with status: "skipped". The event stays in the plan.
• Reassign drops other changes with this notice: In review I only record how the day went, so a change to the plan was skipped.
• A plan with a reflect on a past day: when each planned event of the day has a mark, Reassign confirms the review of the day. It adds the notice Day reviewed. Else it adds <n> events left to review. Reference events do not need a mark.
• A day note longer than 500 characters gives the notice The day note was cut to 500 characters.

Outside review mode, Reassign drops a reflect or a day_note with this notice: Reviews are for a past day, so a review mark was skipped.

The undo token of a command also reverts its day notes and the review confirmation.

Calendar-synced events

In the two modes, you cannot delete a calendar-synced event or move it to the Inbox. Reassign skips the change. For a delete, a park, or a clear, it adds this notice for each event:

"<name>" is synced from a calendar, so the API cannot delete it or move it to the Inbox. Do that in the app.

Run a quick command (Beta)

curl -X POST "https://reassign.app/api/v1/command" \
  -H "Authorization: Bearer rsk_live_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "input": "also coffee with Ana noon, park: write the offsite agenda",
  "mode": "braindump",
  "history": [
    {
      "user": "gym at 7, deep work 9-11",
      "plan": "create \"Gym\" 2026-08-13T07:00 to 2026-08-13T08:00\ncreate \"Deep work\" 2026-08-13T09:00 to 2026-08-13T11:00 (area Work)"
    }
  ]
}'

{
  "date": "2026-08-13",
  "intents": [
    {
      "op": "create",
      "name": "Gym",
      "start": "2026-08-13T07:00",
      "end": "2026-08-13T08:00",
      "areaId": null,
      "activityTypeId": null
    },
    {
      "op": "create",
      "name": "Deep work",
      "start": "2026-08-13T09:00",
      "end": "2026-08-13T11:00",
      "areaId": "3c9d2a41-6b7e-4f80-9a1b-2c3d4e5f6071",
      "activityTypeId": null
    },
    {
      "op": "create",
      "name": "Coffee with Ana",
      "start": "2026-08-13T12:00",
      "end": "2026-08-13T13:00",
      "areaId": null,
      "activityTypeId": null
    },
    {
      "op": "park",
      "name": "Write the offsite agenda",
      "durationMinutes": 60,
      "areaId": null,
      "activityTypeId": null
    }
  ],
  "questions": [],
  "notices": [],
  "undoToken": "00000000-0000-4000-8000-000000000001",
  "expiresAt": "2026-08-13T09:12:00.000Z"
}