Recommended Workflow
Lody currently treats GitHub integration and WorkTrees as core capabilities, so we recommend using them as your default workflow.
Before you start, complete the Quick Start setup.
Break Work into Small Tasks
Because agents have context limits, running several small tasks in parallel usually works better than pushing one large, complex task in a single conversation. Before you begin, split your work into atomic features or fixes. This lets you use worktree-level file isolation for parallel development, which reduces waiting time.
Parallel Development
After splitting requirements, describe one feature or fix per conversation in the home-page composer. In this workflow, one conversation maps to one feature or fix, usually one PR. You can run as many parallel conversations as your machine and context-switching capacity allow.
When Lody finishes a round, it sends a notification. Clicking the notification takes you to the related session. If you are comfortable reading code, review the changed files directly in Lody. If not, copy the branch name under that session in the left sidebar and switch to that branch in your preferred development environment for end-to-end testing.
Once the result is basically ready, click Create PR above the conversation. Lody creates a PR with the full requirement and implementation summary, and links it to the conversation. You can then click the linked PR button to jump directly to the PR on GitHub.
AI Review Loop
If you connect Claude Code, Codex, Devin, or similar tools to your repository, they can review each PR in detail. After review comments arrive, you can ask Lody something like: Fetch PR comments, evaluate whether each point is valid, fix valid issues and mark them resolved, otherwise reply with reasoning. Lody will fetch PR comments, evaluate them, apply fixes, and push a new commit. This triggers the next AI review round (automatically, or manually via @) until no obvious issues remain.
Archive Completed Sessions
When a PR is merged, that session has completed its job. Unless a related bug appears, we do not recommend continuing unrelated work in the same session. Use the archive action in the sidebar to remove completed sessions from your active list.
Periodically Delete Archived Sessions
Archiving only removes sessions from the active list. Archived sessions and their worktrees still consume disk space on the CLI machine, so you should periodically delete archived sessions.
Non-GitHub Projects
This workflow is best for projects hosted on GitHub. We are also working on support for importing arbitrary local projects with the same seamless mobile experience.