The LatchLoop desktop app can work with on your project in the cloud or locally. Here we will cover what you can do with a mapped local repository. This unlocks local editor workflows, an integrated terminal, and a constrained local command runner for agent verification.
Local desktop features require a repository mapping. A mapping connects a GitHub repository to a local folder on your machine.
Once mapped, LatchLoop can:
When the desktop editor detects local changes, it can show a Push All action.
The push dialog lets you:
This is useful when you make small local edits and want to send them back to the task branch without leaving LatchLoop.
The desktop terminal opens a real shell in a mapped repository.
You can open it from:
The terminal is user-driven. The agent cannot type into your interactive terminal. The LatchLoop can however interact with its own sandboxed terminal as described below.
In local mode, the agent may request constrained verification commands such as lint, tests, typecheck, or builds.
These commands run through a policy layer auto approves safe commands, allows you to approve commands you might want to review, and hard denies commands that would be unsafe.
Some commands are not allowed automatically but may be eligible for your approval. When that happens, LatchLoop shows an approval card in the task timeline and pauses the run.
You can approve or reject the command. If approved, the command runs once with that approval. If rejected or expired, the agent receives a controlled denial and continues.
The terminal will not open
The agent says local checks are unavailable
A command was denied