## Provider and model control

Pixcode is provider-neutral at the UI level. Use the provider that fits the task, then keep auth, model selection, and session management in one place.

Claude Code

Use Claude Code sessions, tool output, notifications, and MCP-aware workflows from the Pixcode interface.

OpenAI Codex

Run Codex-backed coding tasks, reviews, and one-shot automation through chat or REST API.

Cursor CLI

Bring Cursor CLI into the same project workspace as the rest of your providers.

Gemini CLI

Use Gemini CLI for Google model workflows without leaving Pixcode.

Qwen Code

Manage Qwen-based coding sessions alongside other agents.

OpenCode

Select OpenCode models and use OpenCode as a first-class worker in orchestration.

## Workspace features

Chat and sessions

Project-aware sessions, provider selection, mode handling, slash command support, and structured tool rendering.

Fixed prompt composer

The main input stays at the bottom of chat/project views so the screen behaves like a real messaging workspace.

Processing visibility

The UI is designed to show when an agent is thinking, running, waiting, or returning output.

Files panel

Browse, open, edit, upload, rename, delete, and inspect files without leaving the agent workflow.

Shell panel

Open the project shell as split view or full view on desktop; use mobile-safe panel behavior on small screens.

Source Control

Review Git status, changed files, diffs, branches, commits, and repository actions.

## Control and automation features

### Changed files Command Center

Tracks local working-tree changes, highlights newly edited files, and opens relevant paths so users can see what an agent changed immediately.

### Multi-agent orchestration

Coordinates multiple agents with roles, labels, instructions, model choices, fallback providers, workflow previews, streaming events, and cancellation.

### API access

External automation can use `px_` API keys for project access, agent runs, orchestration preview/run flows, and integration scripts.

### Notifications

Browser push and Telegram notifications help long-running sessions report completion, failure, or action-required states.

### TaskMaster planning

TaskMaster settings support provider API keys, provider base URLs, and custom OpenAI-compatible API URL/key/model values for planning workflows.

### Open-source readiness

The repository ships with README, LICENSE, contributing guide, code of conduct, security policy, issue templates, releases, screenshots, and static docs.

## Designed for real working loops.

Pixcode is useful because the pieces talk to each other. A prompt can create file changes, the Command Center can show them, Source Control can review them, orchestration can hand work to another agent, and the API can automate the same flow.

Prompt Send work to the provider that fits the task.
Observe See processing state, tool output, shell output, changed files, and orchestration steps.
Review Open changed files, inspect diffs, compare agent reports, and decide what ships.
Automate Use px_ API keys, Telegram, and TaskMaster workflows to keep work moving outside the browser.