AI Integrator PC
Install the desktop application on Mac or Windows, open a local workspace, and connect the runtimes already on the machine.
Install and choose a workspace
AI Integrator PC brings Chat, Code, and Files into the desktop application on Mac and Windows. The current Downloads page links to the installers and public release history. In Code, the project chooser offers Open folder, Clone repository, and Create project. The selected folder gives tasks, files, terminal sessions, worktrees, and Git review a shared working context.
Product switcher
The desktop product switcher keeps Chat, Code, and Files available as distinct destinations. Code can be used without an AI Integrator account for local repository work. Chat and Files remain account-backed services; a signed account can open them from the switcher without moving Code repositories, credentials, or transcripts into account storage. Billing and account settings belong to the account-backed surfaces.
Run controls
The desktop sidebar keeps projects and tasks together. A task composer selects the runtime, model, effort, permission profile, and delegation profile before work begins. The main work area shows the transcript and observable activity. Contextual work surfaces provide Files, Terminal, Git review, Browser, Agents, and usage when the active task supports them. Commit, Push, Merge, Deploy, and Cleanup remain separate actions so a remote or destructive result has its own confirmation.
Local authority
Code uses the coding runtimes and command-line tools installed by the account holder. Settings → Runtimes & Models shows detected connections and opens the vendor setup flow when authentication or an update is required. Vendor credentials stay in the operating system or vendor-owned store. Repositories, branches, worktrees, terminal buffers, local task data, and Code transcripts remain on the machine. AI Integrator does not act as a credential proxy or a hosted Code runner.
Review and remote supervision
The desktop can expose a separate, opt-in Mobile Gateway for a paired phone. The desktop remains authoritative for repository changes, runtime credentials, Git writes, and external actions; the phone receives only the granted task views and scopes. A signed account can provide access to account-backed Chat, Files, and billing without merging those records into the local Code workspace. See Code, Runtimes, Terminal, and Review for the complete desktop loop.