Plan actions
4 actions. Every field marked Required must be sent; account, dryRun, idempotencyKey, confirmCredits and quoteId are the control fields every surface adds.
This week’s plan
Section titled “This week’s plan”plan.week · read
When the user asks what to post (this week or today), start here. The account’s plan for this week, built by Xholic from its goal, sub-topics, results and what’s moving in its circle. Its mode says what the week explores for the account’s stage (new accounts test new lanes, then formats inside proven lanes, then hooks, then small bets) in one line to pass on. Each slot has a day and time, a sub-topic, a mechanism, a format, where the idea comes from, the draft text (or what to write), its status and why it was chosen; plus the week’s test (its slots are marked; a lanes test tries new sub-topics, one or two posts each), one wild card, and the trial lanes with how each is doing. Built on first read if missing. Also cleanup (stale drafts and overdue notes to remove or use) and goalMismatch (when the plan’s posts a day differ from the goal’s). Pass today: true for just today’s slots. Nothing is scheduled until the user approves a slot with approve_plan_slot.
- MCP tool:
get_week_plan. Loaded by default in MCP clients. - REST:
GET /v1/plan/week - CLI:
xholic plan week - Scope:
read - Plan: Every plan, including the trial
- Cost: Free.
- Rate limit bucket:
read
Input
| Field | Type | Required | Description |
|---|---|---|---|
today |
boolean | No | Only today’s slots, in the account’s timezone. |
account |
string ≤ 64 chars | No | X account to act on, as @handle. Leave it out to use the connection’s default account. |
note |
string ≤ 20000 chars | No | Optional, on any tool: one or two sentences for Xholic’s shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. “Dropping threads for now; focusing on replies to founders”). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people’s posts. Leave it out when nothing new was said. |
Change a plan slot
Section titled “Change a plan slot”plan.update_slot · write
Change one slot of this week’s plan: swap its sub-topic (an approved sub-topic id), mechanism, format or time (day and localTime in the account’s timezone), save its text (a post you wrote in the user’s voice for it, with sourcePostId: the proven post from search_inspiration whose shape it borrows), or skip it. Changing the idea clears text that no longer fits, resets where the idea came from, and takes the slot out of the week’s test when it no longer fits it. Text is checked against the user’s own rules; a draft that breaks one or has a detail Xholic can’t back is marked needs_look. It schedules nothing. Approved slots can’t change here (edit the queued post instead).
- MCP tool:
update_plan_slot. Loaded by default in MCP clients. - REST:
POST /v1/plan/update-slot - CLI:
xholic plan update-slot - Scope:
write - Plan: Every plan, including the trial
- Cost: Free.
- Rate limit bucket:
write
Input
| Field | Type | Required | Description |
|---|---|---|---|
slotId |
string ≤ 40 chars | Yes | The slot’s id from get_week_plan (e.g. s-20261124-0930). |
subtopicId |
string ≤ 100 chars | No | An approved sub-topic id. |
mechanism |
“confession_question” \ | “forced_choice” \ | “fresh_finding” \ |
format |
“relatable_scene” \ | “one_liner” \ | “contrast_pair” \ |
day |
string | No | New local date, YYYY-MM-DD. |
localTime |
string | No | New local time, HH:MM. |
text |
string ≤ 25000 chars | No | The post’s text, in the user’s voice. |
sourcePostId |
string | No | The proven post (an X post id from search_inspiration) whose shape the text borrows. Its words are never copied. |
skip |
boolean | No | Skip this slot this week (false brings it back). |
account |
string ≤ 64 chars | No | X account to act on, as @handle. Leave it out to use the connection’s default account. |
note |
string ≤ 20000 chars | No | Optional, on any tool: one or two sentences for Xholic’s shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. “Dropping threads for now; focusing on replies to founders”). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people’s posts. Leave it out when nothing new was said. |
dryRun |
boolean | No | Return exactly what would happen without doing it. |
idempotencyKey |
string ≤ 200 chars | No | A unique key for this write. Repeating a call with the same key returns the first result instead of acting twice. |
Approve a plan slot
Section titled “Approve a plan slot”plan.approve_slot · publish
Schedule one slot of this week’s plan at its time, after the user approved that post in this conversation (one by one; never approve slots on your own initiative, never several on one yes). Pass text to approve with an edit. A slot marked needs_look needs confirmed: true, only after the user said its details are true. The first approved test slot starts the week’s test; its posts are linked to it so the result is judged automatically. It spends post credits when the post goes live: 1 per post, 10 with a link.
- MCP tool:
approve_plan_slot. Loaded by default in MCP clients. - REST:
POST /v1/plan/approve-slot - CLI:
xholic plan approve-slot - Scope:
publish - Plan: Every plan, including the trial
- Cost: Spends a post credit when the post goes live.
- Rate limit bucket:
write - Undo: from the activity log, which runs
queue.unschedule(not offered whenapproved.alreadyScheduledis true: the call changed nothing)
Input
| Field | Type | Required | Description |
|---|---|---|---|
slotId |
string ≤ 40 chars | Yes | The slot’s id from get_week_plan (e.g. s-20261124-0930). |
text |
string ≤ 25000 chars | No | The final text, when the user edited it. |
confirmed |
boolean | No | The user confirmed the details a needs_look draft flagged are true. |
account |
string ≤ 64 chars | No | X account to act on, as @handle. Leave it out to use the connection’s default account. |
note |
string ≤ 20000 chars | No | Optional, on any tool: one or two sentences for Xholic’s shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. “Dropping threads for now; focusing on replies to founders”). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people’s posts. Leave it out when nothing new was said. |
dryRun |
boolean | No | Return exactly what would happen without doing it. |
idempotencyKey |
string ≤ 200 chars | No | A unique key for this write. Repeating a call with the same key returns the first result instead of acting twice. |
Rebuild this week’s plan
Section titled “Rebuild this week’s plan”plan.rebuild · write
Plan the rest of this week again from the current goal, sub-topics and results, for example after the user changed direction or asked for a different week. Approved and scheduled slots stay as they are; the others are replaced. It schedules nothing.
- MCP tool:
rebuild_week_plan. Loaded by default in MCP clients. - REST:
POST /v1/plan/rebuild - CLI:
xholic plan rebuild - Scope:
write - Plan: Every plan, including the trial
- Cost: Free.
- Rate limit bucket:
write
Input
| Field | Type | Required | Description |
|---|---|---|---|
account |
string ≤ 64 chars | No | X account to act on, as @handle. Leave it out to use the connection’s default account. |
note |
string ≤ 20000 chars | No | Optional, on any tool: one or two sentences for Xholic’s shared memory about what the user just decided, asked for or said about themselves or their plans (e.g. “Dropping threads for now; focusing on replies to founders”). Every AI the user connects reads it, so they never repeat themselves. In your words, never other people’s posts. Leave it out when nothing new was said. |
dryRun |
boolean | No | Return exactly what would happen without doing it. |
idempotencyKey |
string ≤ 200 chars | No | A unique key for this write. Repeating a call with the same key returns the first result instead of acting twice. |
