Get started
You can use Doozy in a browser or install the desktop and mobile apps. The fastest setup is to create one workspace around a real project, connect only the tools it needs, and give a small team of Doozies a concrete first outcome.
Before you begin
Have these ready:
- The project, function, or area of life this workspace will own.
- One or two sources of context, such as a document, repository, calendar, inbox, CRM, or shared drive.
- A useful first to-do (aka task or work item) with a result you can evaluate.
- A clear boundary for external actions, spending, deletion, publishing, or account changes.
You can add more context and connections later. A smaller, well-defined workspace is easier to trust than a workspace connected to everything on day one.
1. Open Doozy
Go to usedoozy.com and create an account. Doozy works on the web and through the Doozy desktop app for macOS and Windows. Mobile apps are available for iOS and Android.
Sign in with the same Doozy account on each device. Your workspaces, Doozies, conversations, to-dos, and approvals stay synchronized.
2. Create a workspace
A workspace (aka team space or project space) is the top-level boundary for people, Doozies, connections, files, to-dos, and its Morph environment.
Choose a name tied to durable work, such as Acme customer success, Mobile app launch, or Personal operations. Avoid using one catch-all workspace for unrelated projects that need different data or credentials.
During onboarding, tell Doozy what the workspace is responsible for. A rough description is enough. Doozy researches the context you provide and suggests an initial team.
3. Connect useful apps
Connect services that contain the source material or actions your team needs. Common examples include email, calendar, Slack, Google Drive, GitHub, Linear, Notion, CRM systems, and analytics tools.
Connections (aka connectors or integrations) belong to the workspace. Individual Doozies can be given a smaller toolkit (aka plugin or tool set) drawn from those workspace connections. Start with read access where possible and expand permissions only when the work requires it.
Provider sign-in happens in the provider’s authorization flow. Don’t paste passwords, API keys, verification codes, or session files into chat.
4. Hire your first Doozies
Doozy suggests Doozies (aka AI agents, bots, or teammates) based on the workspace description and connected context. Review each proposed Doozy’s:
- name and role;
- job description;
- responsibilities;
- connected tools;
- approval behavior;
- working hours.
Prefer a small team of focused roles over many overlapping generalists. For a product launch, you might start with a Product Lead, Customer Researcher, and Launch Operator. You can create, edit, archive, or add Doozies later.
5. Give the team a first outcome
Open a conversation with the most relevant Doozy. Explain the outcome in your own words; it doesn’t need to be polished.
Pull together everything in this workspace about the September launch. Tell me what seems unresolved, create to-dos for the important gaps, and draft a launch brief. Ask before messaging anyone outside the workspace.
A strong first handoff usually contains:
- the outcome you want;
- where the relevant evidence probably lives;
- any deadline or quality bar;
- actions that require approval;
- the format of the final result.
Doozy will investigate first. If another Doozy is better suited to part of the work, it can hand off or assign that part while preserving the to-do context.
6. Connect Codex
Open the workspace’s model or provider settings and choose Connect Codex. Complete OpenAI’s browser sign-in to use subscription access, then choose Codex as the model provider for any Doozy or supported to-do. You can alternatively connect an API key for usage-based access.
OpenAI’s official authentication guidance distinguishes ChatGPT subscription sign-in from API-key billing. Your OpenAI plan and workspace policies determine the available Codex usage. Doozy doesn’t turn a plan without Codex access into an eligible plan.
7. Review the work
Use the To-dos list (aka task queue or project list) to see ownership and status, Conversations (aka chats, threads, or sessions) to inspect reasoning and results, Files to open artifacts (aka deliverables or generated files), and Approvals (aka human reviews or confirmations) to accept or reject consequential actions.
Give direct feedback when something is wrong. A correction such as “use the finance team’s weekly format and always show source links” can improve the current result and become durable guidance for that Doozy.
Next steps
- Create and manage Doozies
- Message and orchestrate
- Set up skills, responsibilities, and schedules
- Review security boundaries
Frequently Asked Questions
What do I need before creating a workspace?
You only need an account and a clear first outcome. You can add teammates, connections, files, policies, and model providers as the workspace takes shape.
How long does workspace setup take?
The workspace is available immediately, while Morph may need several minutes to prepare. You can define Doozies and add context while computer-based work waits for Morph to become ready.
How many Doozies should I create first?
Start with two or three roles tied to work you already do. Add another Doozy when it has a distinct outcome, source set, permission boundary, or recurring responsibility.
Can I connect apps later?
Yes. Begin with workspace context and read-only access, then add connections when a real to-do needs them. Grant the smallest useful scopes and expand only when necessary.
Where do I choose Codex as the model provider?
Connect eligible subscription access or an API key in the workspace's model or provider settings. You can then choose Codex for any Doozy or supported to-do.
Looking for something broader? Read the general FAQ.