Use LoopCode

Desktop app

The LoopCode desktop app for macOS, Windows and Linux — projects and sessions, the composer, the built-in browser, change review, terminals, files, Office previews, automations and settings.

#The window

The desktop app has three parts:

• The sidebar — your projects and their sessions (conversations), newest first, with search. ⌘ B hides it.
• The conversation — what you asked, what LoopCode is doing right now, every step it took, and the composer at the bottom.
• The inspector beside it — Browser, Changes, Files and Artifacts tabs on top, and an activity dock with Terminal and Tasks below. Drag its edge to resize it; double-click the edge to reset.

On Windows and Linux, use Ctrl wherever this page says ⌘.

#Projects and sessions

Open a folder with File → Open Project… (⌘ O). Each project keeps its own sessions; LoopCode reopens where you last worked. Start a new session with ⌘ N. The new-session screen asks one question — what should LoopCode do? — and offers four ways in to get you started.

#The composer

The meter under the composer shows how full the context window is and how much of your plan's usage windows are used; click it for details.

#Following the work

While LoopCode works, the conversation shows what it is doing right now, each tool call as it happens, and its own task list pinned to the corner. When it needs you, it asks in the conversation:

• Permission requests — allow once, allow for the session, always allow (written as a rule to your project's local settings), or deny.
• Questions — when it needs a decision, it asks with options to pick from, or you answer in your own words.
• Plans — in Plan mode it shows a plan for you to approve or change before anything is edited.

You can keep typing while it works: a message sent mid-turn steers the current turn.

#Changes

View → Review Changes (⌘ ⇧ D) opens the Changes tab: how much changed, and one file's diff at a time. From there you can undo the turn, commit, or mark it reviewed. The git bar shows the working-tree status while LoopCode works.

#Create a pull request

Create pull request (from the command palette) shows what will happen — the branch, what gets committed, the commits it carries — while LoopCode writes the title and description from the changes. One button commits, pushes and opens the pull request. Without the GitHub CLI, the same button pushes and opens GitHub's page to finish it.

#Browser

The Browser tab is a real Chromium browser with tabs and a saved profile, so your sign-ins stay from one launch to the next. You browse in it; LoopCode drives the tab in front — opening pages, clicking, typing, reading the page and taking screenshots to check its work. File → New Browser Tab (⌘ T) and View → Show Browser (⌘ ⇧ B). See Browser.

#Files

The Files tab shows the project tree with changed files marked, a search across the whole project, and a preview: code with line numbers, Markdown rendered or as source, images. Mention puts the file's @path into your next message.

#Artifacts

When LoopCode makes a Word, PowerPoint or Excel file, the Artifacts tab draws it page by page, with what LoopCode's checks found. Click a page to comment on it, or drag to mark an area — the comment goes to the agent with a picture of the page. Styles lists the looks new documents can take, and takes your own files as templates. See Word, PowerPoint and Excel.

#Terminal and tasks

The Terminal tab lists the commands LoopCode started and left running — a dev server, a watcher — with their state, process ID, output and a stop button. Your own shells sit beside them as real login shells, and keep running when the window reloads. The Tasks tab lists background commands, monitors and subagents. See Subagents and background tasks.

#Command palette

Edit → Search Everything… (⌘ K) finds sessions and runs commands: new session, open workspace, show browser, review changes, create pull request, browse connections, open settings, switch color theme, toggle focus mode, keyboard shortcuts, send feedback, skills and automations.

#Find in a conversation

Edit → Find in Conversation… (⌘ F) searches the open conversation; ⌘ G and ⌘ ⇧ G move between matches. You can copy a response as Markdown, and long messages fold.

#Connections, Skills and Automations

These pages are under the View menu and in the command palette:

• Connections — the directory of MCP servers (GitHub, Linear, Notion, Sentry, Supabase, Stripe and more), connected with one click, plus your own. See MCP servers.
• Skills — the skills LoopCode can use; upload your own. See Skills and commands.
• Automations — scheduled prompts, with their next run. See Goals, loops and automations.

#Control from your phone

File → Control from Phone… shows a QR code. Scan it to follow and steer this computer's sessions from your phone. See Control from your phone.

#Settings

LoopCode → Settings… (⌘ ,):

Settings that belong to a project — permission rules, hooks, MCP servers — live in files you can commit. See Settings.

#Focus mode

Toggle focus mode (command palette) or View → Focus on Conversation hides everything but the conversation.

#Notifications and background work

When a session finishes or needs you while the window is in the background, LoopCode sends a notification that opens that session, and the Dock icon shows how many sessions are waiting. On macOS, closing the window keeps LoopCode running; quitting while a turn is in progress asks first. While LoopCode is working, it keeps your computer from going to sleep.

#Updates

LoopCode checks for updates when it starts and every hour, downloads them in the background, and asks you to restart into the new version. LoopCode → Check for Updates… checks now.

#Keyboard shortcuts