@pixelbyte-software/pixcode 1.38.5 → 1.39.0

package/README.md

@@ -1,9 +1,11 @@
 <div align="center">
-  <img src="public/logo.png" alt="Pixcode logo" width="96" height="96" />
+  <img src="public/logo.png" alt="Pixcode logo" width="92" height="92" />
   <h1>Pixcode</h1>
-  <p><strong>A self-hosted control room for AI coding agents.</strong></p>
+  <p><strong>Self-hosted control plane for AI coding agents.</strong></p>
   <p>
-    Run Claude Code, Cursor CLI, Codex, Gemini CLI, Qwen Code, and OpenCode from one web UI with chat, shell, files, git, orchestration, API keys, plugins, notifications, Telegram, and desktop/server deployment.
+    Pixcode lets you run AI coding CLIs, inspect files, manage shell and source control,
+    orchestrate agent teams, automate through APIs, and keep long-running work alive from
+    your own computer or server.
   </p>
   <p>
     <a href="https://www.npmjs.com/package/@pixelbyte-software/pixcode"><img src="https://img.shields.io/npm/v/@pixelbyte-software/pixcode?style=for-the-badge&color=10b981" alt="npm version" /></a>
@@ -12,7 +14,14 @@
     <img src="https://img.shields.io/badge/Desktop-Windows%20%7C%20macOS%20%7C%20Linux-6366f1?style=for-the-badge" alt="desktop platforms" />
   </p>
   <p>
-    <a href="README.tr.md">Türkçe</a> ·
+    <a href="https://alicomert.github.io/pixcode/landing.html">Website</a> ·
+    <a href="https://github.com/alicomert/pixcode/releases/latest">Releases</a> ·
+    <a href="public/docs.html">Docs</a> ·
+    <a href="public/openapi.yaml">OpenAPI</a> ·
+    <a href="CONTRIBUTING.md">Contributing</a>
+  </p>
+  <p>
+    <a href="README.tr.md">Turkce</a> ·
     <a href="README.de.md">Deutsch</a> ·
     <a href="README.ru.md">Русский</a> ·
     <a href="README.ja.md">日本語</a> ·
@@ -21,93 +30,158 @@
   </p>
 </div>
 
-## What Pixcode Is
+## What Pixcode Does
 
-Pixcode turns your machine, VDS, or workstation into a browser-based AI development cockpit. Instead of jumping between terminals, desktop apps, CLI logs, file explorers, Git tools, and provider dashboards, you get one local web app that understands coding-agent workflows from start to finish.
+Pixcode is a local web and desktop workspace for AI coding agents. It wraps the
+CLIs developers already use, then adds the missing control layer around them:
+project selection, chat history, file navigation, shell access, Git/local change
+tracking, orchestration, notifications, Telegram control, and API automation.
 
-It is designed for three common setups:
+Use it when one terminal is not enough:
 
-- **Local workstation**: run Pixcode on your computer and use it as a richer UI for the CLIs you already trust.
-- **Always-on server**: run it on a Linux server, keep sessions alive, and connect from a laptop, tablet, or phone.
-- **Desktop app**: install `.exe`, `.dmg`, or Linux builds from GitHub releases when you want a packaged app experience.
+- You want Claude Code, Cursor CLI, Codex, Gemini CLI, Qwen Code, and OpenCode
+  available from the same project screen.
+- You want agent output, edited files, shell commands, Git status, and task
+  planning visible without switching tools.
+- You want a server or desktop app that keeps work running while you connect
+  from another computer, tablet, phone, or Telegram.
+- You want a real API surface so other tools can create sessions, run agents,
+  inspect projects, and automate workflows with `px_` API keys.
 
-Pixcode is not a hosted cloud IDE. Your projects, credentials, CLI sessions, local files, Git state, and MCP config stay under your own machine unless you explicitly connect external services.
+Pixcode is not a hosted cloud IDE. Your source code, CLI sessions, credentials,
+project paths, MCP configuration, local database, and automation keys stay on the
+machine where Pixcode runs unless you intentionally expose or connect them.
 
 ## Screenshots
 
 | Workspace control room | Mobile chat |
 | --- | --- |
-| <img src="public/screenshots/desktop-main.png" alt="Pixcode desktop workspace" width="480" /> | <img src="public/screenshots/mobile-chat.png" alt="Pixcode mobile chat" width="260" /> |
+| <img src="public/screenshots/desktop-main.png" alt="Pixcode desktop workspace with chat, project controls, and side panels" width="480" /> | <img src="public/screenshots/mobile-chat.png" alt="Pixcode mobile chat" width="260" /> |
 
 | CLI selection | Tools and MCP |
 | --- | --- |
-| <img src="public/screenshots/cli-selection.png" alt="Pixcode CLI selection" width="420" /> | <img src="public/screenshots/tools-modal.png" alt="Pixcode tools modal" width="420" /> |
+| <img src="public/screenshots/cli-selection.png" alt="Pixcode CLI selection" width="420" /> | <img src="public/screenshots/tools-modal.png" alt="Pixcode tools and MCP modal" width="420" /> |
+
+## Core Features
+
+### Multi-CLI agent workspace
 
-## Highlights
+Pixcode gives every supported coding CLI a shared workspace without hiding the
+provider-native behavior. You can connect the providers you already use and move
+between them from the same project.
 
-### One UI for the CLIs you already use
+- Claude Code
+- Cursor CLI
+- OpenAI Codex
+- Gemini CLI
+- Qwen Code
+- OpenCode
 
-- Claude Code, Cursor CLI, Codex, Gemini CLI, Qwen Code, and OpenCode are available from the same project screen.
-- Provider auth, API-key credentials, OAuth paste flows, install checks, model lists, and CLI version status live under Settings.
-- You can keep using the provider-native CLIs. Pixcode wraps them with session management, web sockets, notifications, file context, and project controls.
-- Processing state is visible while a CLI is thinking, running tools, waiting for approval, or producing output, so the screen does not feel frozen.
+Provider panels cover auth state, install checks, CLI versions, model choices,
+MCP support, and session history. When an agent is thinking, running tools,
+waiting for approval, or writing output, the UI keeps visible processing state
+instead of leaving the screen feeling frozen.
 
-### Chat that feels like a development workspace
+### Chat built for development work
 
-- Project-aware conversations with session history.
-- Fixed bottom prompt composer for focused chat and selected project screens.
-- Mode selection for default/plan/run flows, with mode persistence where the workflow expects it.
-- Slash command support and provider-specific tool rendering.
-- Push and Telegram notifications when long-running agent work finishes, fails, or needs attention.
+Pixcode chat is project-aware and designed for long-running coding sessions.
 
-### Files, shell, and source control without leaving the agent
+- Fixed bottom composer on chat/project screens.
+- Session history per provider and project.
+- Default, plan, and run-style modes where supported.
+- Slash-command friendly input.
+- Tool output rendering for plans, file operations, command output, and provider
+  status events.
+- Telegram and browser/desktop notifications when work finishes, fails, or needs
+  attention.
 
-- Built-in project file browser with edit, upload, rename, delete, and detailed view.
-- Integrated shell panel that can open as split view or full view without losing the main chat/orchestration screen.
-- Source Control panel for Git status, diffs, branches, commits, and changed files.
-- Split panels have compact icon controls, close actions, and half/full behavior for desktop. Mobile uses a screen-appropriate layout instead of trying to force desktop split behavior.
-- The file list is optimized for narrow panels, so permissions and long paths do not dominate the UI.
+### Files, shell, and source control
+
+The side panels are built around the way coding agents change projects.
+
+- Files panel with detailed and compact views.
+- File open/edit flows that preserve the main chat or orchestration surface.
+- Shell panel with split/full behavior on desktop and mobile-safe behavior on
+  smaller screens.
+- Source Control panel for Git status, diffs, branches, commits, and changed
+  files when a project is a Git repository.
+- Local change tracking for projects that are not Git repositories.
 
 ### Command Center for changed files
 
-Pixcode keeps an eye on local working-tree changes, not only GitHub updates. The Quick Settings command mode can show changed files as they appear, highlight them, and jump directly to the edited location.
+Command Center watches what changes while agents work. It can track Git changes
+or local filesystem changes, show the changed file list next to the active chat,
+highlight changed items, and open the edited file at the relevant location.
 
-This is meant for control: when an AI agent edits files, you can see what changed immediately, open the file in the right panel, and keep the main chat or orchestration view visible.
+This is meant to answer the practical question: "What did the agent just touch?"
 
 ### Multi-agent orchestration
 
-The orchestration system is built for more than "send one prompt to one bot." It can coordinate multiple CLI agents around the same goal.
+Pixcode can run structured agent workflows instead of sending every prompt to one
+agent.
 
 Built-in workflow styles include:
 
-- **Agent Team**: split a task across frontend, backend, review, docs, or custom roles.
-- **Multi-model Review**: ask different providers or models to inspect the same implementation.
-- **Sequential Handoff**: pass work through ordered stages when one step depends on the previous result.
-- **Decision Debate**: compare approaches before implementation.
+- Agent Team: split a job across implementation, review, docs, testing, or
+  custom roles.
+- Sequential Handoff: pass compact context from one stage to the next.
+- Multi-model Review: compare provider/model opinions on the same code or plan.
+- Decision Debate: make multiple agents argue approaches before acting.
 
 Orchestration controls include:
 
-- enable/disable agents per run,
-- duplicate a provider when you need multiple workers from the same CLI,
-- assign role, stage, label, and instruction per agent,
-- select the model per agent, including OpenCode model choices,
-- choose a fallback CLI agent for failed steps,
-- preview the workflow DAG before running,
-- stream run events and cancel active runs,
-- resize orchestration side panes so task setup and run output can breathe.
+- per-agent provider and model selection,
+- custom labels, roles, and instructions,
+- duplicate providers when multiple workers should use the same CLI,
+- fallback CLI selection for failed steps,
+- run preview before execution,
+- streamed step output and final report,
+- resizable setup/output panes.
+
+### TaskMaster planning
+
+Pixcode can integrate TaskMaster-backed planning into project work. The Tasks
+tab is meant for PRD parsing, task breakdown, task status, and handing planned
+work to agents.
+
+TaskMaster settings support both known provider variables and custom
+OpenAI-compatible endpoints:
+
+- `ANTHROPIC_API_KEY`
+- `PERPLEXITY_API_KEY`
+- `OPENAI_API_KEY`
+- `OPENAI_BASE_URL`
+- `GOOGLE_API_KEY` / `GEMINI_API_KEY`
+- `OPENROUTER_API_KEY`
+- `AZURE_OPENAI_API_KEY`
+- `AZURE_OPENAI_ENDPOINT`
+- `OLLAMA_BASE_URL`
+- custom OpenAI-compatible API key, API URL, and model fields
+
+For a private gateway, local model router, or third-party OpenAI-compatible
+provider, open Settings, go to Tasks, and set:
+
+- Custom OpenAI-compatible key
+- Custom OpenAI-compatible API URL
+- Custom OpenAI-compatible model, optional
+
+Pixcode maps those values into the environment TaskMaster expects during CLI
+execution, while keeping secret values masked in UI responses.
 
 ### API-first automation
 
-Pixcode's own frontend talks to the backend through REST and WebSocket APIs, and external automation can use the same control plane with Pixcode API keys.
+Pixcode's frontend uses the same backend control plane exposed to external
+automation. Generate a `px_` API key and call the REST/WebSocket APIs from your
+own tools, scripts, CI, dashboards, or Telegram bridge.
 
-New API keys start with `px_`:
+List projects:
 
 ```bash
 curl http://localhost:3001/api/projects \
   -H "Authorization: Bearer px_your_key_here"
 ```
 
-Run a one-shot provider task:
+Run a provider task:
 
 ```bash
 curl http://localhost:3001/api/agent \
@@ -116,7 +190,7 @@ curl http://localhost:3001/api/agent \
   -d '{
     "provider": "codex",
     "projectPath": "/home/me/project",
-    "message": "Review the current diff and list the risky changes.",
+    "message": "Review the current diff and list risky changes.",
     "stream": false
   }'
 ```
@@ -137,50 +211,60 @@ curl http://localhost:3001/api/orchestration/workflows/agent_team/preview \
   }'
 ```
 
-Legacy `ck_` keys remain accepted for older installations, but `px_` is the current prefix.
+Legacy `ck_` keys remain accepted for older installations, but `px_` is the
+current prefix.
 
 OpenAPI reference: [`public/openapi.yaml`](public/openapi.yaml)
 
-### Themes and appearance
+### Telegram, notifications, and remote control
 
-Pixcode now has a real theme system instead of a single blue/navy look.
+Pixcode can pair a Telegram chat with your account so completed tasks, failed
+runs, and action-required states can reach you outside the browser. The goal is
+not just a final notification: the Telegram bridge is a control surface for
+remote prompts, provider/session selection, and long-running work.
 
-- Dark and light modes.
-- Ready-made accent palettes, including emerald and VS Code-like colors.
-- Custom light-mode and dark-mode accent colors.
-- Token-based styling for active states, focus rings, buttons, navigation, and high-emphasis controls.
-- Settings-driven theme changes without rebuilding the app.
+Notification surfaces include:
 
-The goal is to let the UI feel closer to a command-line/development tool when you want it, while still keeping the web app readable on mobile and desktop.
+- in-app alerts,
+- browser/desktop notifications where the platform allows them,
+- Telegram task notifications,
+- update notices and release notes.
 
-### Notifications and Telegram bridge
+### Theme system
 
-- Browser push notifications for long-running CLI sessions.
-- Telegram pairing with short-lived codes.
-- Telegram notifications for completed, failed, or action-required work.
-- Optional bridge behavior so Telegram messages can become prompts for the Pixcode instance.
-- Notification preferences are stored per user.
+Pixcode has a real appearance system instead of one fixed blue/navy palette.
 
-### Plugins and MCP
+- Dark and light modes.
+- Ready-made accent palettes, including emerald and VS Code-like options.
+- Custom accent colors for dark and light themes.
+- Token-based styling for focus rings, active controls, buttons, navigation, and
+  panels.
+
+### MCP and plugins
 
-Pixcode includes optional extension points:
+Pixcode includes extension points for local workflows:
 
 - MCP server management for supported providers.
-- Provider-specific MCP/session/auth panels.
-- Plugin loading with frontend tabs and optional backend services.
-- Local settings for API keys, base URLs, model catalogs, and provider install status.
+- Provider-specific auth, MCP, and sessions panels.
+- Plugin loading with optional frontend tabs and backend services.
+- Local settings for API keys, base URLs, model catalogs, and provider install
+  state.
 
 ## Installation
 
-### Run with npx
+### Requirements
 
-Requires Node.js 22 or newer.
+- Node.js 22 or newer.
+- The provider CLIs you want to use, installed and authenticated separately when
+  required.
+
+### Run with npx
 
 ```bash
 npx @pixelbyte-software/pixcode
 ```
 
-Then open:
+Open:
 
 ```text
 http://localhost:3001
@@ -195,21 +279,24 @@ pixcode
 
 ### Desktop installers
 
-Download desktop builds from GitHub releases:
+Download desktop builds from GitHub Releases:
 
 - Windows: `.exe`
 - macOS: `.dmg`
-- Linux: AppImage / package builds depending on the release asset
+- Linux: AppImage or package asset, depending on the release
 
 Releases: <https://github.com/alicomert/pixcode/releases/latest>
 
 #### macOS Gatekeeper: "Pixcode is damaged"
 
-Current macOS desktop builds are unsigned. If macOS says `Pixcode is damaged and can't be opened. You should move it to the Trash`, first make sure the DMG came from the official Pixcode GitHub Releases page, then:
+Current macOS desktop builds can be unsigned. If macOS says `Pixcode is damaged
+and can't be opened. You should move it to the Trash`, first make sure the DMG
+came from the official Pixcode GitHub Releases page, then:
 
 1. Open the DMG and drag `Pixcode.app` into `/Applications`.
 2. Double-click `Fix Gatekeeper.command` inside the mounted DMG.
-3. Pixcode will remove the quarantine flag from `/Applications/Pixcode.app` and open normally.
+3. Pixcode removes the quarantine flag from `/Applications/Pixcode.app` and can
+   open normally.
 
 Manual fallback:
 
@@ -220,7 +307,7 @@ open "/Applications/Pixcode.app"
 
 ### Linux daemon
 
-For a server/VDS setup:
+For a server or VDS setup:
 
 ```bash
 pixcode daemon install --mode auto --port 3001
@@ -237,20 +324,22 @@ pixcode --no-daemon
 
 ### Ports
 
-- Backend and bundled frontend: `SERVER_PORT`, default `3001`.
+- Installed backend and bundled frontend: `SERVER_PORT`, default `3001`.
 - Vite-only frontend development: `VITE_PORT`, default `5173`.
 
-For normal installed usage, think in terms of one port: `3001`. The `5173` port is only for separate Vite frontend development.
+For normal installed usage, think in terms of one port: `3001`. Port `5173` is
+only for separate Vite frontend development.
 
-## First Run Checklist
+## First Run
 
 1. Open Pixcode and create or sign in to the local user account.
 2. Add the project folders you want to manage.
 3. Connect the CLI providers you actually use.
 4. Open Settings and check provider install/auth/model status.
-5. Generate a `px_` API key if you want automation, CI, Telegram, or external tools to talk to Pixcode.
-6. Pick your theme palette under Appearance.
-7. Enable notifications if you want long-running sessions to report back.
+5. Enable TaskMaster if you want planning and task execution flows.
+6. Generate a `px_` API key for external automation.
+7. Pair Telegram if you want remote prompts and completion notifications.
+8. Pick your theme palette under Appearance.
 
 ## Development
 
@@ -264,33 +353,75 @@ npm run build
 Important development notes:
 
 - `npm run dev` uses the daemon manager on Linux.
-- For a foreground development loop, run `npm run client` and `npm run server` separately, or run `pixcode --no-daemon`.
-- `npm run server` runs built output from `dist-server/`; rebuild after backend changes.
-- There is no unit test suite configured today. Use typecheck, lint, build, and manual provider/API checks.
+- For a foreground development loop, run `npm run client` and `npm run server`
+  separately, or run `pixcode --no-daemon`.
+- `npm run server` runs built output from `dist-server/`; rebuild after backend
+  changes.
+- There is no unit test suite configured today. Use smoke scripts, typecheck,
+  lint, build, and manual provider/API checks.
 
 ## Repository Map
 
 - `src/` - React + Vite frontend.
-- `server/` - Express, WebSocket, CLI adapters, routes, auth, daemon, notifications.
-- `server/modules/orchestration/` - multi-agent workflow engine and A2A adapters.
-- `server/modules/providers/` - provider auth, MCP, sessions, model and install endpoints.
+- `server/` - Express, WebSocket, CLI adapters, routes, auth, daemon,
+  notifications.
+- `server/modules/orchestration/` - multi-agent workflow engine and A2A
+  adapters.
+- `server/modules/providers/` - provider auth, MCP, sessions, model and install
+  endpoints.
 - `shared/` - contracts shared by frontend and backend.
 - `public/openapi.yaml` - API reference shipped with the app.
-- `public/screenshots/` - README/product screenshots.
+- `public/screenshots/` - README and product screenshots.
+- `public/llms.txt` and `public/llms-full.txt` - AI-discovery summaries.
+
+## Open Source Readiness
+
+Pixcode is prepared for public contribution with the basics contributors expect:
+
+- Clear README with purpose, install commands, screenshots, API examples, and
+  architecture map.
+- Open-source license in [`LICENSE`](LICENSE).
+- Contribution guide in [`CONTRIBUTING.md`](CONTRIBUTING.md).
+- Code of conduct in [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md).
+- Security policy in [`SECURITY.md`](SECURITY.md).
+- GitHub issue templates for bug reports, feature requests, and good first
+  issues.
+- Releases and version tags published through GitHub Releases.
+- Static website and documentation under [`public/`](public).
+
+Good starter work should be labeled `good first issue` on GitHub. The repository
+also includes a good-first-issue template so small, scoped tasks can be filed
+without losing context.
 
 ## Security Model
 
 - Pixcode is self-hosted. Treat it like a local control plane for your machine.
 - Use strong local account credentials when exposing it on a network.
-- Put it behind a trusted reverse proxy/VPN when running on a public server.
+- Put public-server deployments behind a trusted reverse proxy, VPN, or firewall.
 - API keys are intended for automation. Rotate them if they are exposed.
 - Provider secrets are masked in APIs and UI responses where possible.
+- Do not publish logs that contain provider tokens, session output, or private
+  project paths.
+
+## Contributing
+
+Read [`CONTRIBUTING.md`](CONTRIBUTING.md) before opening a pull request. Keep
+changes scoped, run the verification commands above, and include screenshots or
+short recordings for UI work when possible.
+
+For community behavior expectations, read
+[`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md). For private vulnerability reports,
+read [`SECURITY.md`](SECURITY.md).
 
 ## Links
 
+- Website: <https://alicomert.github.io/pixcode/landing.html>
 - npm: <https://www.npmjs.com/package/@pixelbyte-software/pixcode>
 - GitHub: <https://github.com/alicomert/pixcode>
 - Releases: <https://github.com/alicomert/pixcode/releases/latest>
 - API docs: [`public/openapi.yaml`](public/openapi.yaml)
 - Static docs: [`public/docs.html`](public/docs.html), [`public/features.html`](public/features.html), [`public/orchestration.html`](public/orchestration.html), [`public/api-automation.html`](public/api-automation.html)
 - AI discovery: [`public/llms.txt`](public/llms.txt), [`public/llms-full.txt`](public/llms-full.txt)
+
+Pixcode is an independent open-source project and is not affiliated with OpenAI,
+Anthropic, Google, Cursor, Alibaba/Qwen, OpenCode, or TaskMaster.

package/SECURITY.md

@@ -0,0 +1,46 @@
+# Security Policy
+
+Pixcode is a self-hosted control plane for local projects, provider CLIs, API
+keys, Telegram pairing, shell access, files, Git state, and agent sessions. Treat
+it like sensitive developer infrastructure.
+
+## Supported Versions
+
+Security fixes are targeted at the latest published release and the current
+`main` branch.
+
+| Version | Supported |
+| --- | --- |
+| Latest release | Yes |
+| Older releases | Best effort |
+
+## Reporting a Vulnerability
+
+Please do not open a public issue for private vulnerabilities, leaked tokens, or
+exploit details.
+
+Use GitHub Security Advisories for this repository when available. If advisory
+reporting is not available, contact the repository owner privately through
+GitHub and include:
+
+- affected Pixcode version or commit,
+- operating system and deployment mode,
+- reproduction steps,
+- expected impact,
+- relevant logs with secrets removed.
+
+## Deployment Guidance
+
+- Do not expose Pixcode directly to the public internet without a trusted reverse
+  proxy, VPN, firewall, or equivalent access control.
+- Use strong local account credentials.
+- Rotate `px_` API keys and provider tokens if they are exposed.
+- Do not paste production provider tokens into public issues or screenshots.
+- Keep desktop installers and npm packages updated from official Pixcode
+  releases.
+
+## Scope
+
+Reports are most useful when they involve Pixcode application code, API
+authorization, session isolation, secret handling, desktop packaging, update
+behavior, or unsafe shell/file access.