Message and orchestrate

Conversations (aka chats, threads, or sessions) are where you delegate, clarify, review, and redirect work. To-dos (aka tasks or work items) keep ownership and progress visible. Tabs (aka task contexts, work contexts, or sessions) let you keep several pieces of work open without mixing their histories. Doozy connects all three so people and Doozies can work in parallel without losing the shape of the outcome.

Message a Doozy

Open Conversations, start a new conversation, and select a Doozy. Describe the outcome in normal language. You can include files, links, dates, people, examples, and boundaries.

Doozy is designed to act on imperfect requests. Before asking you to fill in details, it searches the workspace, relevant app connections, prior to-dos, and available files. When multiple reasonable interpretations would materially change the result, it presents the options instead of silently choosing.

For important work, make these explicit:

• the desired outcome;
• the deadline or priority;
• what evidence should support the result;
• actions that require approval;
• what should be preserved if the plan changes.

Let Doozy choose the team

You don’t always need to pick a Doozy first. Start with a broad workspace request and Doozy can identify the appropriate roles, create to-dos, assign ownership, and establish dependencies.

Prepare us for the Acme renewal next week. Find what changed, identify risk, update the internal account plan, and draft the meeting brief. Don’t send anything to Acme.

The account-health Doozy might inspect usage and support history, a finance Doozy might verify commercial terms, and an executive-operations Doozy might assemble the final brief. The interface shows those assignments and their status without requiring you to build a flowchart.

Redirect work in progress

Send a correction in the active conversation. State what changed and what remains valid.

The deadline moved to Thursday. Keep the research and analysis, drop the slide deck, and turn the recommendation into a one-page memo.

Direct user guidance takes priority over the previous plan. Completed external actions can’t be undone by a message, so use approvals for actions where reversal would be costly.

When a conversation is busy, new guidance joins a visible queue and sends after the current run. You can review or remove queued messages before they send, which lets you add the next instruction without interrupting work already underway.

Keep each piece of work in a tab

Workspace tabs behave like browser tabs for active work. Open a conversation, to-do, or capture in its own tab, switch between them, pin important work, and leave a running task open while you inspect something else.

A Doozy is the durable role; a tab is one work context. The same Sales Doozy can research an account in one tab, prepare a renewal brief in another, and keep an outreach review open in a third. Each conversation keeps its own messages, files, decisions, and queued guidance.

This separation supports three useful patterns:

• one Doozy working across several independent tasks;
• several Doozies contributing to one coordinated outcome;
• both patterns running at the same time in one workspace.

Create and assign to-dos

To-dos make delegated work inspectable. A to-do can include an owner, priority, due date, schedule (aka routine, recurring task, or timed automation), files, status, and a linked conversation. Doozies can create child to-dos or assign work to another Doozy when that’s the clearest route to the outcome.

Use to-do ownership to show accountability, not every internal reasoning step. A to-do should represent a result someone can recognize as complete.

Doozy handoffs

A handoff includes the objective, relevant context, source links, existing artifacts, constraints, and expected output. The receiving Doozy can access the same workspace records and Morph environment, so it doesn’t need a pasted transcript of everything that happened.

The originating Doozy remains responsible for integrating the delegated result unless to-do ownership was explicitly transferred. When Doozies disagree, the coordinator should compare evidence and surface the unresolved decision to you.

Coordinate several Doozies

Several Doozies can contribute to one outcome when the work benefits from different roles. A coordinator can create focused to-dos, assign owners, track dependencies, and combine the results. This works well for researching accounts, reviewing separate files, testing several hypotheses, or drafting distinct parts of a launch plan.

Parallel Doozies still share one Morph environment per workspace. Use separate branches, directories, or other coordination conventions when simultaneous engineering to-dos could modify the same files. Doozy should reconcile changes before presenting a final result.

Share the workspace with people

Workspace members can open the same conversations, to-dos, captures, files, and approvals according to their role. They can respond in a to-do conversation, edit shared work, assign a to-do to another member or Doozy, and see status changes as they happen. Mention a teammate when their judgment or action is needed, so the decision stays attached to the work.

Each member can arrange their own tabs around the work they need to watch. The shared records underneath those tabs stay synchronized, so a teammate can continue a thread or update a to-do without asking its original creator to relay the context.

External recipients don’t gain workspace access merely because a Doozy drafts a message about them. Sharing a conversation or artifact creates a deliberate review surface; check the contents before sharing.

Find prior work

Search Conversations by participant, status, date, or text. Search to-dos and files when you remember the outcome but not the conversation.

You can also ask a Doozy to recover prior context:

Find the last decision about the migration timeline. Link the original evidence, explain what has changed since then, and don’t treat old assumptions as current facts.

Keep collaboration effective

• Assign one accountable owner for the final result.
• Ask for evidence and links when facts matter.
• Separate facts, inference, and recommendations.
• Use to-dos for durable ownership and conversations for steering.
• Keep external actions behind approval until the workflow is proven.
• Correct work directly; Doozies can save useful feedback as memory.

Frequently Asked Questions