Once LatchLoop has helped you plan and define your task, the Build action starts a background agent in LatchLoop to work on your task. For tasks already defined in tools such as Linear, outside of LatchLoop, you can tag LatchLoop to have it import and automatically start the task.
If you set LatchLoop to auto-build for your project, then LatchLoop will automatically gather the context it feels is important in order to create a pull request.
If you choose to manually the build phase, you are able to adjust the context that LatchLoop sees manually before a pull request is created.
Once a pull request is created, you can use the sidebar chat that will become available to request changes or to ask questions. LatchLoop should be thought of as a teammate. You can freely work on the same branch that LatchLoop has created, and it will be able to understand any changes that your team has made to the branch outside of LatchLoop.
Once a pull request is merged, LatchLoop will automatically mark the task as completed.
Using the A key on your keyboard, you can toggle the file contents that LatchLoop feels are related to this task.
Once toggled, you can use the F key or slash key on your keyboard to activate the file search input and add additional files from your repository to LatchLoop’s context. If you want to remove files LatchLoop has already added to the context tray, you can use the number keys (1-9) on your keyboard to toggle the respective files in the context.
If you plan to use an external tool to build, please see our article on Copying Prompts linked below.