Step 1: Open Coddo
Launch Coddo from your Applications folder. If this is your first time, complete the onboarding flow first.Step 2: Create or open a project
From the sidebar, you have two options:Create a new project
- Click New Project from the sidebar
- Choose a parent directory where the project folder will be created
- Enter a project name
- Coddo creates the folder and initializes it
Open an existing project
- Click Open Project from the sidebar
- Navigate to your existing project folder
- Coddo detects the project and initializes the
.coddo/directory
Step 3: Understand the project structure
When Coddo initializes a project, it creates a.coddo/ directory:
The
.coddo/ directory is local to your machine. It is automatically added to .gitignore by Coddo.Step 4: Set up CLAUDE.md / AGENTS.md
Before chatting with your agent, create aCLAUDE.md (Claude Code) or AGENTS.md (Codex) file to give it context about your project. Use the built-in editor or create it manually — Coddo can also generate both with AI from your codebase.
Key things to include:
- Your tech stack and frameworks
- Build and run commands
- Coding conventions
- Important project rules
Step 5: Create your first tasks
Switch to the Kanban view and start creating tasks:- Click + New Task
- Write a descriptive title
- Add detailed instructions for the agent
- Choose a provider (Claude Code or Codex), a model, and an execution mode (worktree or direct)
- Optionally add tags and attach images
- The task appears in the Backlog column
Step 6: Start coding with your agent
- Move a task to Todo - Coddo’s queue runner automatically picks it up
- Watch the task move to In Progress as the agent starts working
- Click on the task to see the live conversation in the detail panel
- When done, the task moves to Review - check the changes
- Validate and merge (worktree) or commit (direct), then move to Done
Tips for success
- Write clear instructions - The more specific your task instructions, the better the agent’s output
- Use worktree mode for independent tasks that can run in parallel
- Review changes carefully - Check the diff before merging
- Iterate - If the first attempt isn’t right, send another message from the review state