An AI conversation is a useful place to talk through a week. It becomes less useful when the resulting task list stays inside the conversation and has to be copied into a planner.
WeekOrbit connects those two parts of the workflow. It is a weekly-view task planner with Today, Week, Month, and Group views. You can move tasks by dragging them, use its built-in AI assistant to add, organize, and update tasks by chat, or connect an external assistant through MCP or the open API.
Disclosure: I build WeekOrbit. This is an example of how its planning workflow can be used, rather than a benchmark or a claim about productivity gains.
Start with a plan you can inspect
A weekly board gives a conversation somewhere concrete to land. Before asking an assistant to make changes, look at the tasks already scheduled and decide which part of the plan needs attention.
For example, you might want to review today's unfinished tasks rather than reorganize the entire month. That distinction matters: asking for a review and asking for changes are different requests.
Use conversation for a specific change
The built-in assistant supports task changes through chat. MCP and the open API also allow external assistants to work with the same plan.
One possible workflow is to ask an assistant to list today's tasks, choose which ones need attention, and then request specific updates. Connection and tool support depend on the external assistant you use.
This does not require treating an assistant as the owner of your schedule. You can use it for the parts where conversation helps, then return to the visual planner to review the result and move tasks yourself.
Keep the planning horizon visible
Today answers what needs attention now. Week shows how tasks are distributed across the next few days. Month provides a wider view, and Groups offer another way to organize the same work.
Those views make it possible to move between a focused task list and the surrounding week. An example routine is to review the Week view, pick today's work in Today, and revisit the week when priorities change.
The free tier includes 20 built-in AI turns per day; Pro includes 500. Those limits describe the built-in assistant, not an external assistant's own subscription or usage limits.
You can explore the planner at https://weekorbit.com.
For developers connecting assistants to personal tools, the useful design question is this: after a conversation changes a task, how easily can the person inspect and adjust that change in the product?
Top comments (1)
The distinction between reviewing and changing the plan is useful. I'd show a conflicting-edit example across the two interfaces: an assistant reads a task, the person drags it to Friday, then the assistant submits an update based on the old date. Does the update reject the stale revision, merge only the requested fields, or silently move it back? A before/after view should identify the exact changed fields and actor. Undo is worth testing after a later manual edit too, so undoing the assistant's change doesn't erase the person's newer work.