StepCue

Summarize a completed or ended StepCue focus session. Use this only when the StepCue widget reaches the end of a session or the user explicitly asks what they accomplished in the completed session. Do not use this tool when the user asks for the next task, next session, another session, or to continue working; in those cases use create_focus_session only. Do not use this tool for a casual message like "I am done" unless the widget has just ended a concrete session and provides counts. Otherwise respond briefly in chat. Use only the provided session counts, task label, and focus minutes. Do not request saved history, analytics, or conversation history. Return a short completion summary and one small next-session suggestion. Do not create dashboards, streaks, rankings, long coaching text, or content that completes the user task.

complete_focus_session

Create or open the StepCue task-start app. Use this only when the user wants to start, plan, or open a focused study/work timer from a task list or a short task description. Do not use this tool for ordinary questions, direct requests to write/solve/explain content, or requests to send emails/messages unless the user explicitly asks to start a focus session, timer, study session, or work sprint. If the latest user message has a task and a time, create a session immediately. If it has a task but no time, ask only: "How much time do you want to give this? For example: 20 minutes, 45 minutes, 2 hours, or say you choose." If it has time but no concrete task, ask what the user wants to work on. Generic study intent is valid when paired with time. For example, "study for 1 hour", "1 hour study session", and "revise for 45 minutes" are enough to create a general study session; do not ask what subject unless the user only asks to focus/work without mentioning study or revision. Pass latestUserMessage only as the exact latest user message. Do not include assistant messages, previous user messages, summaries, raw chat history, or any extra context. Do not reuse an earlier task for a fresh generic request like "I want a 5 hour study session" unless the latest message clearly says same, that, these, previous, continue, next, next task, or is a direct answer to the app asking for duration. Treat an earlier multi-task dump as a short task queue only while the user is explicitly continuing it. Track the named tasks in the conversation: if the user says "next", "next task", or "continue" and exactly one named task from that queue has not had its own session yet, create a session for that remaining task immediately and set reusePreviousTaskContext=true. If two or more named tasks remain after a vague "next", ask the user to choose between those remaining tasks. If no named tasks remain, ask what they want to work on next. Never say the original list is finished until every named task in it has had a session. Do not create repeated follow-up sessions from vague "next" messages once the original task queue is exhausted. Never invent cycles such as refresh, follow-up, final check, or one more push unless the user names that task. If the user says "you choose", "I do not know", "pick for me", or still does not provide a time after being asked once, choose a sensible duration and set letAiDecideDuration=true. If the user says they do not know where to start, feels overwhelmed, or dumps several big tasks without a clear time, choose one best first task. Do not create a 2-hour plan for everything. When letAiDecideDuration=true and the user gave multiple big tasks without a specific time, choose the best first focus session instead of creating a full schedule. Pick one priority task, prefer 25-45 minutes, and leave the other tasks for later. Only split multiple big tasks across blocks when the user provided a clear total time. If the task quantity is unrealistic for the time, make a progress session. Do not promise completion; prioritize best-fit, highest-impact, or first useful progress. Respect explicit constraints: use requested durations up to 120 minutes, cap longer active sessions to the first 120 minutes, honor no breaks, break length, and break interval requests. Default breaks should be light. Do not add breaks under 60 minutes unless the user asks. For 60-120 minute sessions, use at most one break unless the user explicitly asked for a break interval. When building timerBlocks, split multiple tasks into a few concrete focus/break blocks. Keep focus blocks at 90 minutes or less, break blocks at 30 minutes or less, and make durations add up to durationMinutes. Keep instructions short, practical, and task-specific. The widget shows one block at a time, so every block title and instruction must stand alone. Do not write, solve, draft, send, or complete homework, essays, emails, applications, code, or other task content unless the user explicitly asks for that separate help. Do not write a separate numbered plan, schedule, or task instructions in chat after calling this tool. The widget is the plan. After a successful session creation, reply with one short sentence only. Do not use this tool for severe distress, self-harm, medical emergencies, or unsafe requests such as using pills to stay awake. Respond safely in chat instead. After a successful session creation, keep the assistant response brief, such as "I started a focus session for this."

create_focus_session

Create a short reset action when the user says they got distracted or the widget requests a distraction reset. Use only the current step title, current step instruction, and distraction count. Do not request or pass full conversation history. Return one practical physical reset and one concrete resume action for the current block. Keep the copy short, calm, and non-judgmental. Do not re-plan the session or add general productivity advice.

handle_distraction