User documentation

Glixo Code user guide

Glixo Code is a cross-device agentic coding app. You choose a project, connect a model provider, start a session, and let the agent read files, edit code, run commands, and explain what changed. You stay in control through permission prompts, review surfaces, checkpoints, and notifications.

Install and sign in

1. Open Downloads and install the Windows desktop app or Android APK.
2. Launch Glixo Code and sign in with your Glixo account.
3. Choose how the agent should run: use the browser sandbox for zero-install work, or connect a desktop target machine for full local filesystem and terminal access.
4. Open Settings - Providers and add at least one LLM provider account.

The browser sandbox keeps setup light: it can use terminal, files, git, and app preview in a cached WebAssembly Linux environment. A connected target machine is better when the agent needs your real repository, native tools, local apps, or desktop integration.

Add model providers

Provider accounts are scoped credentials used by agent sessions. Provider ids stay stable, but the add-account screen uses plain labels so the choice is obvious:

OpenAI, Anthropic, OpenAI browser login, and Ollama ship as bundled LLM providers. CLIProxy is first-party but installable from the extension catalog. OneDrive and Dropbox are installable storage providers, not bundled providers.

Add storage providers

OneDrive and Dropbox are optional community storage modules. Install one from Extensions, then open Settings - Storage and connect the account with browser sign-in. Glixo owns the OAuth callback and token storage; the provider module only declares metadata, scopes, and capabilities.

• Inline is the default attachment mode. Files stay in Glixo and the runtime injects supported content into the LLM request.
• Cloud link uploads the attachment to the selected storage provider, asks for a short-lived raw download URL, probes that URL, then sends the URL to the LLM provider. If the provider is missing or the probe fails, Glixo falls back to inline.
• Replication can use a connected storage provider that advertises the Replication capability. Filesystem/shared-folder replication remains available separately.

Managed builds can provide default public-client ids for normal users. Advanced users can type their own client id in the connect form. App registrations should allow the loopback redirect URIs http://127.0.0.1:1456/auth/callback for OneDrive and http://127.0.0.1:1457/auth/callback for Dropbox.

Settings

Settings are split by what they control, so account-wide defaults, project defaults, workspace overrides, and extension grants stay understandable.

• Settings - Providers manages provider accounts, keys, browser login accounts, and the default provider account used when a launch does not specify one.
• Settings - Storage lists installed storage providers, connects storage accounts, and chooses inline or cloud-link attachment delivery.
• Settings - Agent stores account-level Code defaults: model routing, reasoning level, permission mode, MCP presets, system prompt mode, custom system prompt text, and global rules.
• Project profile - Run defaults stores shared project defaults for model, reasoning, permission mode, MCP presets, project rules, and project system prompt. New workspaces under the project inherit these defaults.
• Workspace settings stay thin: they mainly override target machine, folder, labels, memory-pack location, and optional workspace rules.
• Settings - Extensions manages extension install/update/uninstall, target-machine placement, lifecycle operations, logs, catalog sources, and granted capabilities.

Effective launch defaults resolve from the launch/session choice first, then project defaults, then account defaults. Workspace settings can still override machine, path, runtime choices, MCP presets, and workspace rules when a specific workspace needs them.

Start an agent session

1. Open or create a workspace.
2. Pick the target machine or browser sandbox.
3. Select a provider account, model, reasoning level, and permission mode.
4. Describe the task in the composer. Be specific about files, tests, constraints, and what done means.

During a session, the main chat shows user and agent messages. The right rail shows supporting views such as files, changes, session stats, and notifications. Use checkpoints before risky edits so you can return to a known-good state.

Permissions and safety

Glixo Code is designed for human-in-the-loop work. The agent can propose commands and edits, but permission settings decide what it may do automatically.

• Ask is best while learning a repo or using a new tool.
• Plan/review modes help with larger changes before edits start.
• More permissive modes are useful only after the workspace and command surface are trusted.

Native approve, deny, stop, or retry actions are intentionally not performed directly from system notifications. Notifications open the correct session UI so existing approval controls handle the decision.

Notifications

The notification drawer lives in the right rail. Use it to review agent contact messages, approval requests, completed runs, failed runs, workflow gates, schedule updates, and system notices.

Clicking a notification opens the relevant session or workflow view. Approval notifications focus the approval controls; completion and failure notifications focus the latest session activity.

Agxos mode

Agxos is the embedded agentic OS inside Glixo. Use it when the task is less about editing an existing repo and more about creating, forking, running, or replaying small apps.

• App Creator turns a prompt into a runnable app.
• Catalog apps can be installed, forked, and changed.
• Replays make sessions shareable as small browser links.

Extensions

Extensions add IDE panels, tools, skills, LLM provider definitions, storage provider definitions, and Agxos apps. Browse installable modules at extend.glixo.io.

Install opens Glixo Code through a deep link. After installation, LLM provider extensions appear in Settings - Providers, storage provider extensions appear in Settings - Storage, and UI/tool extensions appear in their contributed surfaces.

Agent contribution controls live under the Agent settings view. For each installed extension, you can allow or block whole categories: agent tools, skills, and MCP servers. Per-item toggles are intentionally deferred so v1 uses the same audited capability grants as extension install consent.

Shared agent memory is a core Glixo Code feature, not something installed as an extension. Memory-related extensions can add views or read-only tools, but the storage boundary stays owned by the app runtime.

Troubleshooting