Getting started

1. Add a project

Start Loom, then add the absolute path to a local Git repository from the workspace sidebar. The repository needs at least one commit. Configure your Git author name and email so task branches can be committed.

Choose a small, verifiable change for your first run. A documentation correction or a focused bug fix makes it easier to follow the complete workflow.

2. Start with a conversation

Select your project and send a message. OpenCode is the default runtime; you can also choose a connected Claude Code, Codex CLI, or Antigravity CLI provider in chat. Type @ to find project files or choose a custom agent. A custom agent uses the provider and model configured for that agent.

Sessions keep their own conversation history. Open tabs for separate threads, and use the split view to work with two chats side by side. The selected model, custom agent, and thinking mode apply to each message, so check the composer before sending if you changed them between turns.

File changes, tool activity, and the response appear in the conversation. Context usage is shown when the provider returns token metadata; some providers do not report it.

3. Turn a goal into a plan

Create a plan for work that benefits from several tasks. Describe the goal and expected result. Review the proposed task titles, prompts, dependencies, and project commands.

Edit the plan before starting. Only approve install, lint, test, and build commands you understand. They run for the task workflow and can access the machine with your user permissions.

4. Review the result

Follow task states in the Kanban board and inspect their conversations. When tasks finish, open the integration review. Read the combined diff and check results, including any failed checks and repair attempts.

Make the main project checkout clean before approving the merge. Approval applies to the exact reviewed commit. If the integration changes, review its new head again.