@pixelbyte-software/pixcode 1.55.1 → 1.55.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (172) hide show
  1. package/dist-server/server/modules/tasks/git-worktree.js +98 -0
  2. package/dist-server/server/modules/tasks/git-worktree.js.map +1 -0
  3. package/dist-server/server/modules/tasks/index.js +8 -0
  4. package/dist-server/server/modules/tasks/index.js.map +1 -0
  5. package/dist-server/server/modules/tasks/prompt-builder.js +85 -0
  6. package/dist-server/server/modules/tasks/prompt-builder.js.map +1 -0
  7. package/dist-server/server/modules/tasks/role-presets.js +94 -0
  8. package/dist-server/server/modules/tasks/role-presets.js.map +1 -0
  9. package/dist-server/server/modules/tasks/runners/claude-runner.js +109 -0
  10. package/dist-server/server/modules/tasks/runners/claude-runner.js.map +1 -0
  11. package/dist-server/server/modules/tasks/runners/codex-runner.js +67 -0
  12. package/dist-server/server/modules/tasks/runners/codex-runner.js.map +1 -0
  13. package/dist-server/server/modules/tasks/runners/spawn-runner.js +111 -0
  14. package/dist-server/server/modules/tasks/runners/spawn-runner.js.map +1 -0
  15. package/dist-server/server/modules/tasks/runners/types.js +5 -0
  16. package/dist-server/server/modules/tasks/runners/types.js.map +1 -0
  17. package/dist-server/server/modules/tasks/scheduler.js +69 -0
  18. package/dist-server/server/modules/tasks/scheduler.js.map +1 -0
  19. package/dist-server/server/modules/tasks/task-queue.js +81 -0
  20. package/dist-server/server/modules/tasks/task-queue.js.map +1 -0
  21. package/dist-server/server/modules/tasks/task-routes.js +195 -0
  22. package/dist-server/server/modules/tasks/task-routes.js.map +1 -0
  23. package/dist-server/server/modules/tasks/task-runner.js +187 -0
  24. package/dist-server/server/modules/tasks/task-runner.js.map +1 -0
  25. package/dist-server/server/modules/tasks/task-store.js +196 -0
  26. package/dist-server/server/modules/tasks/task-store.js.map +1 -0
  27. package/dist-server/server/modules/tasks/task-types.js +5 -0
  28. package/dist-server/server/modules/tasks/task-types.js.map +1 -0
  29. package/dist-server/server/modules/tasks/user-interaction.js +73 -0
  30. package/dist-server/server/modules/tasks/user-interaction.js.map +1 -0
  31. package/package.json +1 -1
  32. package/server/modules/tasks/git-worktree.ts +102 -0
  33. package/server/modules/tasks/index.ts +9 -0
  34. package/server/modules/tasks/prompt-builder.ts +98 -0
  35. package/server/modules/tasks/role-presets.ts +113 -0
  36. package/server/modules/tasks/runners/claude-runner.ts +120 -0
  37. package/server/modules/tasks/runners/codex-runner.ts +80 -0
  38. package/server/modules/tasks/runners/spawn-runner.ts +122 -0
  39. package/server/modules/tasks/runners/types.ts +25 -0
  40. package/server/modules/tasks/scheduler.ts +75 -0
  41. package/server/modules/tasks/task-queue.ts +91 -0
  42. package/server/modules/tasks/task-routes.ts +245 -0
  43. package/server/modules/tasks/task-runner.ts +219 -0
  44. package/server/modules/tasks/task-store.ts +223 -0
  45. package/server/modules/tasks/task-types.ts +100 -0
  46. package/server/modules/tasks/user-interaction.ts +93 -0
  47. package/server/routes/auth.js +13 -6
  48. package/dist/api-automation.html +0 -110
  49. package/dist/api-docs.html +0 -548
  50. package/dist/assets/KaTeX_AMS-Regular-BQhdFMY1.woff2 +0 -0
  51. package/dist/assets/KaTeX_AMS-Regular-DMm9YOAa.woff +0 -0
  52. package/dist/assets/KaTeX_AMS-Regular-DRggAlZN.ttf +0 -0
  53. package/dist/assets/KaTeX_Caligraphic-Bold-ATXxdsX0.ttf +0 -0
  54. package/dist/assets/KaTeX_Caligraphic-Bold-BEiXGLvX.woff +0 -0
  55. package/dist/assets/KaTeX_Caligraphic-Bold-Dq_IR9rO.woff2 +0 -0
  56. package/dist/assets/KaTeX_Caligraphic-Regular-CTRA-rTL.woff +0 -0
  57. package/dist/assets/KaTeX_Caligraphic-Regular-Di6jR-x-.woff2 +0 -0
  58. package/dist/assets/KaTeX_Caligraphic-Regular-wX97UBjC.ttf +0 -0
  59. package/dist/assets/KaTeX_Fraktur-Bold-BdnERNNW.ttf +0 -0
  60. package/dist/assets/KaTeX_Fraktur-Bold-BsDP51OF.woff +0 -0
  61. package/dist/assets/KaTeX_Fraktur-Bold-CL6g_b3V.woff2 +0 -0
  62. package/dist/assets/KaTeX_Fraktur-Regular-CB_wures.ttf +0 -0
  63. package/dist/assets/KaTeX_Fraktur-Regular-CTYiF6lA.woff2 +0 -0
  64. package/dist/assets/KaTeX_Fraktur-Regular-Dxdc4cR9.woff +0 -0
  65. package/dist/assets/KaTeX_Main-Bold-Cx986IdX.woff2 +0 -0
  66. package/dist/assets/KaTeX_Main-Bold-Jm3AIy58.woff +0 -0
  67. package/dist/assets/KaTeX_Main-Bold-waoOVXN0.ttf +0 -0
  68. package/dist/assets/KaTeX_Main-BoldItalic-DxDJ3AOS.woff2 +0 -0
  69. package/dist/assets/KaTeX_Main-BoldItalic-DzxPMmG6.ttf +0 -0
  70. package/dist/assets/KaTeX_Main-BoldItalic-SpSLRI95.woff +0 -0
  71. package/dist/assets/KaTeX_Main-Italic-3WenGoN9.ttf +0 -0
  72. package/dist/assets/KaTeX_Main-Italic-BMLOBm91.woff +0 -0
  73. package/dist/assets/KaTeX_Main-Italic-NWA7e6Wa.woff2 +0 -0
  74. package/dist/assets/KaTeX_Main-Regular-B22Nviop.woff2 +0 -0
  75. package/dist/assets/KaTeX_Main-Regular-Dr94JaBh.woff +0 -0
  76. package/dist/assets/KaTeX_Main-Regular-ypZvNtVU.ttf +0 -0
  77. package/dist/assets/KaTeX_Math-BoldItalic-B3XSjfu4.ttf +0 -0
  78. package/dist/assets/KaTeX_Math-BoldItalic-CZnvNsCZ.woff2 +0 -0
  79. package/dist/assets/KaTeX_Math-BoldItalic-iY-2wyZ7.woff +0 -0
  80. package/dist/assets/KaTeX_Math-Italic-DA0__PXp.woff +0 -0
  81. package/dist/assets/KaTeX_Math-Italic-flOr_0UB.ttf +0 -0
  82. package/dist/assets/KaTeX_Math-Italic-t53AETM-.woff2 +0 -0
  83. package/dist/assets/KaTeX_SansSerif-Bold-CFMepnvq.ttf +0 -0
  84. package/dist/assets/KaTeX_SansSerif-Bold-D1sUS0GD.woff2 +0 -0
  85. package/dist/assets/KaTeX_SansSerif-Bold-DbIhKOiC.woff +0 -0
  86. package/dist/assets/KaTeX_SansSerif-Italic-C3H0VqGB.woff2 +0 -0
  87. package/dist/assets/KaTeX_SansSerif-Italic-DN2j7dab.woff +0 -0
  88. package/dist/assets/KaTeX_SansSerif-Italic-YYjJ1zSn.ttf +0 -0
  89. package/dist/assets/KaTeX_SansSerif-Regular-BNo7hRIc.ttf +0 -0
  90. package/dist/assets/KaTeX_SansSerif-Regular-CS6fqUqJ.woff +0 -0
  91. package/dist/assets/KaTeX_SansSerif-Regular-DDBCnlJ7.woff2 +0 -0
  92. package/dist/assets/KaTeX_Script-Regular-C5JkGWo-.ttf +0 -0
  93. package/dist/assets/KaTeX_Script-Regular-D3wIWfF6.woff2 +0 -0
  94. package/dist/assets/KaTeX_Script-Regular-D5yQViql.woff +0 -0
  95. package/dist/assets/KaTeX_Size1-Regular-C195tn64.woff +0 -0
  96. package/dist/assets/KaTeX_Size1-Regular-Dbsnue_I.ttf +0 -0
  97. package/dist/assets/KaTeX_Size1-Regular-mCD8mA8B.woff2 +0 -0
  98. package/dist/assets/KaTeX_Size2-Regular-B7gKUWhC.ttf +0 -0
  99. package/dist/assets/KaTeX_Size2-Regular-Dy4dx90m.woff2 +0 -0
  100. package/dist/assets/KaTeX_Size2-Regular-oD1tc_U0.woff +0 -0
  101. package/dist/assets/KaTeX_Size3-Regular-CTq5MqoE.woff +0 -0
  102. package/dist/assets/KaTeX_Size3-Regular-DgpXs0kz.ttf +0 -0
  103. package/dist/assets/KaTeX_Size4-Regular-BF-4gkZK.woff +0 -0
  104. package/dist/assets/KaTeX_Size4-Regular-DWFBv043.ttf +0 -0
  105. package/dist/assets/KaTeX_Size4-Regular-Dl5lxZxV.woff2 +0 -0
  106. package/dist/assets/KaTeX_Typewriter-Regular-C0xS9mPB.woff +0 -0
  107. package/dist/assets/KaTeX_Typewriter-Regular-CO6r4hn1.woff2 +0 -0
  108. package/dist/assets/KaTeX_Typewriter-Regular-D3Ib7_Hf.ttf +0 -0
  109. package/dist/assets/index-B-ySsQqi.js +0 -877
  110. package/dist/assets/index-CWO38aJI.css +0 -32
  111. package/dist/assets/index-ak1p_4ew.js +0 -11
  112. package/dist/assets/localMonaco-DFIbtDNp.js +0 -1
  113. package/dist/assets/vendor-codemirror-CIYNS698.js +0 -41
  114. package/dist/assets/vendor-react-DB6V5Fl1.js +0 -59
  115. package/dist/assets/vendor-xterm-C7tpxJl7.js +0 -9
  116. package/dist/clear-cache.html +0 -85
  117. package/dist/convert-icons.md +0 -53
  118. package/dist/docs.html +0 -308
  119. package/dist/favicon.png +0 -0
  120. package/dist/favicon.svg +0 -8
  121. package/dist/features.html +0 -133
  122. package/dist/generate-icons.js +0 -49
  123. package/dist/humans.txt +0 -15
  124. package/dist/icons/claude-ai-icon.svg +0 -1
  125. package/dist/icons/codex-white.svg +0 -3
  126. package/dist/icons/codex.svg +0 -3
  127. package/dist/icons/cursor-white.svg +0 -12
  128. package/dist/icons/cursor.svg +0 -1
  129. package/dist/icons/gemini-ai-icon.svg +0 -1
  130. package/dist/icons/icon-128x128.png +0 -0
  131. package/dist/icons/icon-128x128.svg +0 -9
  132. package/dist/icons/icon-144x144.png +0 -0
  133. package/dist/icons/icon-144x144.svg +0 -9
  134. package/dist/icons/icon-152x152.png +0 -0
  135. package/dist/icons/icon-152x152.svg +0 -9
  136. package/dist/icons/icon-192x192.png +0 -0
  137. package/dist/icons/icon-192x192.svg +0 -9
  138. package/dist/icons/icon-384x384.png +0 -0
  139. package/dist/icons/icon-384x384.svg +0 -9
  140. package/dist/icons/icon-512x512.png +0 -0
  141. package/dist/icons/icon-512x512.svg +0 -9
  142. package/dist/icons/icon-72x72.png +0 -0
  143. package/dist/icons/icon-72x72.svg +0 -9
  144. package/dist/icons/icon-96x96.png +0 -0
  145. package/dist/icons/icon-96x96.svg +0 -9
  146. package/dist/icons/icon-template.svg +0 -9
  147. package/dist/icons/opencode-logo-dark.svg +0 -1
  148. package/dist/icons/opencode-logo-light.svg +0 -1
  149. package/dist/icons/qwen-ai-icon.png +0 -0
  150. package/dist/icons/qwen-logo.svg +0 -15
  151. package/dist/index.html +0 -62
  152. package/dist/landing.html +0 -268
  153. package/dist/llms-full.txt +0 -119
  154. package/dist/llms.txt +0 -53
  155. package/dist/logo-128.png +0 -0
  156. package/dist/logo-256.png +0 -0
  157. package/dist/logo-32.png +0 -0
  158. package/dist/logo-512.png +0 -0
  159. package/dist/logo-64.png +0 -0
  160. package/dist/logo.png +0 -0
  161. package/dist/logo.svg +0 -12
  162. package/dist/manifest.json +0 -61
  163. package/dist/openapi.yaml +0 -1696
  164. package/dist/orchestration.html +0 -125
  165. package/dist/robots.txt +0 -4
  166. package/dist/screenshots/cli-selection.png +0 -0
  167. package/dist/screenshots/desktop-main.png +0 -0
  168. package/dist/screenshots/mobile-chat.png +0 -0
  169. package/dist/screenshots/tools-modal.png +0 -0
  170. package/dist/site.css +0 -692
  171. package/dist/sitemap.xml +0 -51
  172. package/dist/sw.js +0 -132
package/dist/clear-cache.html DELETED
@@ -1,85 +0,0 @@
1
- <!DOCTYPE html>
2
- <html>
3
- <head>
4
- <title>Clear Cache - Claude Code UI</title>
5
- <style>
6
- body {
7
- font-family: system-ui, -apple-system, sans-serif;
8
- max-width: 600px;
9
- margin: 50px auto;
10
- padding: 20px;
11
- line-height: 1.6;
12
- }
13
- .success { color: green; }
14
- .error { color: red; }
15
- button {
16
- background: #007bff;
17
- color: white;
18
- border: none;
19
- padding: 10px 20px;
20
- border-radius: 5px;
21
- cursor: pointer;
22
- font-size: 16px;
23
- margin: 10px 5px;
24
- }
25
- button:hover {
26
- background: #0056b3;
27
- }
28
- #status {
29
- margin-top: 20px;
30
- padding: 15px;
31
- border-radius: 5px;
32
- background: #f0f0f0;
33
- }
34
- </style>
35
- </head>
36
- <body>
37
- <h1>Clear Cache & Service Worker</h1>
38
- <p>If you're seeing a blank page or old content, click the button below to clear all cached data.</p>
39
-
40
- <button onclick="clearEverything()">Clear Cache & Reload</button>
41
-
42
- <div id="status"></div>
43
-
44
- <script>
45
- async function clearEverything() {
46
- const status = document.getElementById('status');
47
- status.innerHTML = '<p>Clearing cache and service workers...</p>';
48
-
49
- try {
50
- // Unregister all service workers
51
- if ('serviceWorker' in navigator) {
52
- const registrations = await navigator.serviceWorker.getRegistrations();
53
- for (let registration of registrations) {
54
- await registration.unregister();
55
- status.innerHTML += '<p class="success">✓ Unregistered service worker</p>';
56
- }
57
- }
58
-
59
- // Clear all caches
60
- if ('caches' in window) {
61
- const cacheNames = await caches.keys();
62
- for (let cacheName of cacheNames) {
63
- await caches.delete(cacheName);
64
- status.innerHTML += `<p class="success">✓ Deleted cache: ${cacheName}</p>`;
65
- }
66
- }
67
-
68
- // Clear localStorage
69
- localStorage.clear();
70
- status.innerHTML += '<p class="success">✓ Cleared localStorage</p>';
71
-
72
- // Clear sessionStorage
73
- sessionStorage.clear();
74
- status.innerHTML += '<p class="success">✓ Cleared sessionStorage</p>';
75
-
76
- status.innerHTML += '<p class="success"><strong>✓ All caches cleared!</strong></p>';
77
- status.innerHTML += '<p>Cache cleared successfully. You can now close this tab or <a href="/">go to home page</a>.</p>';
78
-
79
- } catch (error) {
80
- status.innerHTML += `<p class="error">✗ Error: ${error.message}</p>`;
81
- }
82
- }
83
- </script>
84
- </body>
85
- </html>
package/dist/convert-icons.md DELETED
@@ -1,53 +0,0 @@
1
- # Convert SVG Icons to PNG
2
-
3
- I've created SVG versions of the app icons that match the MessageSquare design from the sidebar. To convert them to PNG format, you can use one of these methods:
4
-
5
- ## Method 1: Online Converter (Easiest)
6
- 1. Go to https://cloudconvert.com/svg-to-png
7
- 2. Upload each SVG file from the `/icons/` directory
8
- 3. Download the PNG versions
9
- 4. Replace the existing PNG files
10
-
11
- ## Method 2: Using Node.js (if you have it)
12
- ```bash
13
- npm install sharp
14
- node -e "
15
- const sharp = require('sharp');
16
- const fs = require('fs');
17
- const sizes = [72, 96, 128, 144, 152, 192, 384, 512];
18
- sizes.forEach(size => {
19
- const svgPath = \`./icons/icon-\${size}x\${size}.svg\`;
20
- const pngPath = \`./icons/icon-\${size}x\${size}.png\`;
21
- if (fs.existsSync(svgPath)) {
22
- sharp(svgPath).png().toFile(pngPath);
23
- console.log(\`Converted \${svgPath} to \${pngPath}\`);
24
- }
25
- });
26
- "
27
- ```
28
-
29
- ## Method 3: Using ImageMagick (if installed)
30
- ```bash
31
- cd public/icons
32
- for size in 72 96 128 144 152 192 384 512; do
33
- convert "icon-${size}x${size}.svg" "icon-${size}x${size}.png"
34
- done
35
- ```
36
-
37
- ## Method 4: Using Inkscape (if installed)
38
- ```bash
39
- cd public/icons
40
- for size in 72 96 128 144 152 192 384 512; do
41
- inkscape --export-type=png "icon-${size}x${size}.svg"
42
- done
43
- ```
44
-
45
- ## Icon Design
46
- The new icons feature:
47
- - Clean MessageSquare (chat bubble) design matching the sidebar
48
- - Primary color background with rounded corners
49
- - White stroke icon that's clearly visible
50
- - Consistent sizing and proportions across all sizes
51
- - Proper PWA-compliant format
52
-
53
- Once converted, the PNG files will replace the existing ones and provide a consistent icon experience across all platforms.
package/dist/docs.html DELETED
@@ -1,308 +0,0 @@
1
- <!doctype html>
2
- <html lang="en">
3
- <head>
4
- <meta charset="utf-8" />
5
- <meta name="viewport" content="width=device-width, initial-scale=1" />
6
- <title>Pixcode Documentation - Complete Self-hosted AI Coding Agent Guide</title>
7
- <meta
8
- name="description"
9
- content="Complete Pixcode documentation covering Claude Code, Cursor CLI, OpenAI Codex, Gemini CLI, Qwen Code, OpenCode, VS Code-style workspaces, files, terminal panels, Git/local changes, orchestration, API keys, Telegram, notifications, MCP, plugins, themes, desktop installers, and Linux server deployment."
10
- />
11
- <meta
12
- name="keywords"
13
- content="Pixcode documentation, Claude Code web UI documentation, Codex UI documentation, Cursor CLI web interface, AI coding agent orchestration docs, Orchestration, OpenCode UI docs, MCP server manager, local AI coding assistant, self-hosted coding agent dashboard"
14
- />
15
- <meta name="robots" content="index,follow,max-image-preview:large,max-snippet:-1" />
16
- <link rel="canonical" href="https://alicomert.github.io/pixcode/docs.html" />
17
- <link rel="icon" href="favicon.png" />
18
- <link rel="stylesheet" href="site.css" />
19
- <meta property="og:title" content="Pixcode Documentation" />
20
- <meta property="og:description" content="A complete guide to Pixcode features, setup, orchestration, API automation, providers, plugins, MCP, Telegram, themes, and deployment." />
21
- <meta property="og:image" content="screenshots/desktop-main.png" />
22
- <script type="application/ld+json">
23
- {
24
- "@context": "https://schema.org",
25
- "@type": "TechArticle",
26
- "headline": "Pixcode Documentation",
27
- "about": [
28
- "AI coding agents",
29
- "Claude Code UI",
30
- "OpenAI Codex UI",
31
- "multi-agent orchestration",
32
- "self-hosted developer tools"
33
- ],
34
- "description": "Complete documentation for Pixcode, a self-hosted AI coding agent control room.",
35
- "author": {
36
- "@type": "Organization",
37
- "name": "Pixcode Contributors"
38
- }
39
- }
40
- </script>
41
- </head>
42
- <body>
43
- <nav class="site-nav" aria-label="Main navigation">
44
- <a class="brand" href="landing.html">
45
- <img src="logo.png" alt="" />
46
- <span>Pixcode</span>
47
- </a>
48
- <div class="nav-links">
49
- <a href="docs.html">Documentation</a>
50
- <a href="features.html">Features</a>
51
- <a href="orchestration.html">Orchestration</a>
52
- <a href="api-automation.html">API</a>
53
- <a href="https://github.com/alicomert/pixcode">GitHub</a>
54
- </div>
55
- </nav>
56
-
57
- <header class="hero docs-hero">
58
- <div>
59
- <div class="eyebrow">Complete documentation</div>
60
- <h1>Pixcode from start to finish.</h1>
61
- <p class="lead">
62
- Pixcode is a self-hosted control plane for AI coding agents. This page explains the full system: providers, chat, files, shell, source control, orchestration, API keys, Telegram, notifications, plugins, MCP, themes, desktop builds, Linux daemon mode, and development workflow.
63
- </p>
64
- </div>
65
- <div class="image-slot">
66
- <span><strong>Documentation hero image slot</strong>Recommended: 1400 x 1000. Show a clean overview of Pixcode with chat, panels, provider status, and orchestration.</span>
67
- </div>
68
- </header>
69
-
70
- <main class="section">
71
- <div class="grid sidebar">
72
- <aside class="toc" aria-label="Documentation table of contents">
73
- <a href="#overview">Overview</a>
74
- <a href="#providers">Provider support</a>
75
- <a href="#workspace">Workspace UI</a>
76
- <a href="#command-center">Changed files</a>
77
- <a href="#orchestration">Orchestration</a>
78
- <a href="#background-workflows">Background workflows</a>
79
- <a href="#api">API and automation</a>
80
- <a href="#telegram">Notifications and Telegram</a>
81
- <a href="#plugins">Plugins and MCP</a>
82
- <a href="#themes">Themes</a>
83
- <a href="#install">Install and deployment</a>
84
- <a href="#security">Security</a>
85
- <a href="#development">Development</a>
86
- </aside>
87
-
88
- <div class="doc-content">
89
- <section id="overview" class="doc-section">
90
- <h2>Overview</h2>
91
- <p>
92
- Pixcode gives developers one browser-based workspace for AI coding CLIs. The app runs locally or on a server, serves a React/Vite frontend, and exposes an Express/WebSocket backend that controls provider processes, project files, Git state, shell sessions, notifications, and orchestration workflows.
93
- </p>
94
- <p>
95
- The core idea is simple: keep the provider-native command line tools, but add a serious control surface around them. A coding agent can edit files, run commands, wait for permissions, fail, recover, or hand work to another model. Pixcode is designed to make those states visible and manageable instead of hiding them behind a blank terminal.
96
- </p>
97
- <div class="grid two">
98
- <div class="card">
99
- <strong>Who it is for</strong>
100
- <p>Developers, solo builders, teams, educators, and automation-heavy users who want to run AI coding agents on their own machine or server.</p>
101
- </div>
102
- <div class="card">
103
- <strong>What it is not</strong>
104
- <p>Pixcode is not a hosted cloud IDE and not an official OpenAI, Anthropic, Google, Cursor, Qwen, or OpenCode product.</p>
105
- </div>
106
- </div>
107
- </section>
108
-
109
- <section id="providers" class="doc-section">
110
- <h2>Provider support</h2>
111
- <p>
112
- Pixcode currently targets Claude Code, Cursor CLI, OpenAI Codex, Gemini CLI, Qwen Code, and OpenCode. Each provider can have its own authentication flow, model list, session handling, MCP behavior, CLI installation status, and runtime output style.
113
- </p>
114
- <ul class="feature-list">
115
- <li>Claude Code support with sessions, hooks, notifications, and MCP-related provider settings.</li>
116
- <li>Codex support for OpenAI-backed coding workflows and REST-triggered automation.</li>
117
- <li>Cursor CLI support for developers who already keep Cursor CLI in their local workflow.</li>
118
- <li>Gemini CLI support for Google model workflows.</li>
119
- <li>Qwen Code support for Qwen-based coding flows.</li>
120
- <li>OpenCode support with model selection and free/open provider use cases.</li>
121
- </ul>
122
- <div class="image-slot wide">
123
- <span><strong>Provider settings image slot</strong>Recommended: 1600 x 900. Show provider auth status, model refresh, API key/base URL fields, and CLI version update notices.</span>
124
- </div>
125
- </section>
126
-
127
- <section id="workspace" class="doc-section">
128
- <h2>Workspace UI</h2>
129
- <p>
130
- The Pixcode workspace is organized around the active project. The main area can be a chat screen or the orchestration system, depending on what the user is doing. Supporting panels such as Shell, Files, and Source Control can open alongside the main view, so the user does not lose context.
131
- </p>
132
- <h3>Chat</h3>
133
- <p>
134
- Chat is project-aware and session-based. The prompt composer stays fixed at the bottom of the screen in the main chat/project view. Users can switch providers and modes, send multiline messages, use slash commands, and review tool output in structured components.
135
- </p>
136
- <h3>Shell</h3>
137
- <p>
138
- The shell panel gives direct project terminal access from inside the browser. On desktop, the panel can open as a split view first and expand to a full panel if needed. On mobile, the layout avoids desktop-only split behavior and adapts to the smaller screen.
139
- </p>
140
- <h3>Files</h3>
141
- <p>
142
- The file browser supports project navigation, file opening, editing, upload, rename, delete, and detailed metadata. Narrow-panel behavior is tuned so long names and permissions do not consume the entire view.
143
- </p>
144
- <h3>Source Control</h3>
145
- <p>
146
- Source Control shows Git status, changed files, diffs, branches, commits, and repository actions. It is designed to be close to agent work, because code-generating agents must be reviewed through actual diffs, not only through chat summaries.
147
- </p>
148
- <div class="screen-grid">
149
- <img src="screenshots/desktop-main.png" alt="Pixcode workspace screenshot" />
150
- <img src="screenshots/mobile-chat.png" alt="Pixcode mobile chat screenshot" />
151
- </div>
152
- </section>
153
-
154
- <section id="command-center" class="doc-section">
155
- <h2>Changed files command center</h2>
156
- <p>
157
- Pixcode can watch Git changes or local filesystem changes. In Quick Settings, the Command Center view can show changed files as they appear, highlight newly modified paths, and open the related file location. This helps users keep control when an AI agent edits multiple files quickly, even when the project is not a Git repository.
158
- </p>
159
- <p>
160
- The important design point is that this does not depend on GitHub pushes. It works with local changes, so the user can review the agent's work before committing, pushing, tagging, or publishing.
161
- </p>
162
- <div class="image-slot">
163
- <span><strong>Changed files image slot</strong>Recommended: 1200 x 900. Show Quick Settings with changed file list, green highlight, and right panel file preview.</span>
164
- </div>
165
- </section>
166
-
167
- <section id="orchestration" class="doc-section">
168
- <h2>Multi-agent orchestration</h2>
169
- <p>
170
- Pixcode orchestration coordinates multiple child agents around one goal. The workflow layer uses adapter-backed tasks, shared context, per-agent metadata, run events, preview endpoints, cancellation, and a UI that lets users resize the setup and output panes.
171
- </p>
172
- <ul class="feature-list">
173
- <li>Agent Team for role-based work distribution.</li>
174
- <li>Multi-model Review for independent review from different providers or models.</li>
175
- <li>Sequential Handoff for ordered workflows where later steps depend on earlier output.</li>
176
- <li>Decision Debate for comparing approaches before implementation.</li>
177
- <li>Per-agent label, role, model, instruction, and fallback CLI selection.</li>
178
- <li>Workflow DAG preview before execution.</li>
179
- <li>Run event streaming and cancellation.</li>
180
- </ul>
181
- <p>
182
- For deeper orchestration details, see <a href="orchestration.html">orchestration.html</a>.
183
- </p>
184
- </section>
185
-
186
- <section id="background-workflows" class="doc-section">
187
- <h2>Background workflows</h2>
188
- <p>
189
- Pixcode uses orchestration for project-aware background workflow, review, and verification tasks. It runs inside the current Pixcode instance, understands the selected project, and routes work to the configured CLI provider.
190
- </p>
191
- <p>
192
- Orchestration APIs expose agent metadata, workflow state, project-scoped task history, streamed output, and artifacts under authenticated endpoints.
193
- </p>
194
- <div class="code-panel"><pre><code>GET /api/orchestration/agents
195
- GET /api/orchestration/tasks
196
- GET /api/orchestration/workflows/runs/:runId</code></pre></div>
197
- </section>
198
-
199
- <section id="api" class="doc-section">
200
- <h2>API and automation</h2>
201
- <p>
202
- Pixcode is API-first internally: the frontend communicates with the backend through REST and WebSocket APIs. External tools can use Pixcode API keys for automation. New keys use the `px_` prefix, while older `ck_` keys remain accepted for compatibility.
203
- </p>
204
- <div class="code-panel"><pre><code>curl http://localhost:3001/api/projects \
205
- -H "Authorization: Bearer px_your_key_here"</code></pre></div>
206
- <p>
207
- Automation can list projects, run one-shot provider tasks, preview orchestration graphs, start workflow runs, stream events, cancel work, and integrate Pixcode into CI, scripts, dashboards, or Telegram-style bridges.
208
- </p>
209
- <p>
210
- See <a href="api-automation.html">api-automation.html</a> and <a href="openapi.yaml">openapi.yaml</a>.
211
- </p>
212
- </section>
213
-
214
- <section id="telegram" class="doc-section">
215
- <h2>Notifications and Telegram</h2>
216
- <p>
217
- Long-running agent tasks should report back. Pixcode includes browser push notification support and a Telegram pairing flow. Users can receive notifications when sessions complete, fail, or require action. Telegram bridge behavior can route messages back into the Pixcode instance when enabled.
218
- </p>
219
- <div class="image-slot">
220
- <span><strong>Telegram and notification image slot</strong>Recommended: 1200 x 900. Show notification settings, Telegram pairing code, and a task completion notification.</span>
221
- </div>
222
- </section>
223
-
224
- <section id="plugins" class="doc-section">
225
- <h2>Plugins and MCP</h2>
226
- <p>
227
- Pixcode includes extension points for provider tools, MCP server management, and plugins. Provider-specific settings can manage MCP configuration, sessions, API-key credentials, OAuth paste flows, install jobs, and model catalogs. Plugins can add frontend tabs and optional backend services.
228
- </p>
229
- <ul class="feature-list">
230
- <li>MCP server management for supported providers.</li>
231
- <li>Provider auth and session panels.</li>
232
- <li>Model refresh and CLI install status.</li>
233
- <li>Plugin loader support for UI tabs and backend integrations.</li>
234
- </ul>
235
- </section>
236
-
237
- <section id="themes" class="doc-section">
238
- <h2>Themes and appearance</h2>
239
- <p>
240
- Pixcode supports dark/light mode, built-in accent palettes, VS Code-like colors, emerald command-style colors, and custom accent values for dark and light modes. Theme tokens affect buttons, active states, focus rings, navigation, and other high-emphasis UI parts together.
241
- </p>
242
- <div class="grid two">
243
- <div class="image-slot">
244
- <span><strong>Dark theme slot</strong>Recommended: 1200 x 900. Show a terminal-like dark UI with emerald or amber accents.</span>
245
- </div>
246
- <div class="image-slot">
247
- <span><strong>Light theme slot</strong>Recommended: 1200 x 900. Show custom accent color and readable light mode.</span>
248
- </div>
249
- </div>
250
- </section>
251
-
252
- <section id="install" class="doc-section">
253
- <h2>Install and deployment</h2>
254
- <p>
255
- Pixcode targets Node.js 22+. The recommended quick start is npx or a global npm installation. Normal installed runtime serves the backend and built frontend through port 3001. Vite port 5173 is only for separate frontend development.
256
- </p>
257
- <div class="grid three">
258
- <div class="code-panel"><pre><code>npx @pixelbyte-software/pixcode</code></pre></div>
259
- <div class="code-panel"><pre><code>npm install -g @pixelbyte-software/pixcode
260
- pixcode</code></pre></div>
261
- <div class="code-panel"><pre><code>pixcode daemon install --mode auto --port 3001
262
- pixcode daemon status --mode auto</code></pre></div>
263
- </div>
264
- <p>
265
- Desktop installers are published from GitHub releases for Windows `.exe`, macOS `.dmg`, and Linux package/AppImage-style assets depending on the release.
266
- </p>
267
- </section>
268
-
269
- <section id="security" class="doc-section">
270
- <h2>Security model</h2>
271
- <p>
272
- Pixcode can control project files, shell sessions, Git state, provider CLIs, API keys, and external notification channels. Treat it like a powerful local admin interface. Use strong account credentials, rotate exposed API keys, and put public server deployments behind trusted network controls such as a reverse proxy, firewall, or VPN.
273
- </p>
274
- <ul class="feature-list">
275
- <li>Local account login protects the web UI.</li>
276
- <li>API keys are for automation and should be scoped operationally by where they are stored.</li>
277
- <li>Provider secrets should not be exposed in logs, screenshots, public pages, or issue reports.</li>
278
- <li>Remote deployments should be treated as sensitive developer infrastructure.</li>
279
- </ul>
280
- </section>
281
-
282
- <section id="development" class="doc-section">
283
- <h2>Development workflow</h2>
284
- <p>
285
- The frontend is React + Vite. The backend is Express + WebSocket with provider routes, orchestration modules, SQLite-backed auth data, and CLI adapter files. There is no unit test suite configured today; use typecheck, lint, build, and targeted manual smoke checks.
286
- </p>
287
- <div class="code-panel"><pre><code>npm install
288
- npm run typecheck
289
- npm run lint
290
- npm run build</code></pre></div>
291
- <p>
292
- Important: `npm run dev` starts the daemon manager on Linux. For separate frontend development, use `npm run client`. For built backend runtime, rebuild before `npm run server`.
293
- </p>
294
- </section>
295
- </div>
296
- </div>
297
- </main>
298
-
299
- <footer class="footer">
300
- <strong>Pixcode documentation</strong> ·
301
- <a href="landing.html">Home</a> ·
302
- <a href="features.html">Features</a> ·
303
- <a href="orchestration.html">Orchestration</a> ·
304
- <a href="api-automation.html">API</a> ·
305
- <a href="llms.txt">llms.txt</a>
306
- </footer>
307
- </body>
308
- </html>
package/dist/favicon.png DELETED
Binary file
package/dist/favicon.svg DELETED
@@ -1,8 +0,0 @@
1
- <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 500 500" width="32" height="32">
2
- <g transform="translate(250 250) scale(1.25) translate(-250 -250)">
3
- <g transform="translate(0 500) scale(0.1 -0.1)" fill="#5C3FFC">
4
- <path d="M2037 3800 c-104 -40 -191 -134 -231 -250 -23 -67 -20 -82 22 -109 31 -20 287 -177 1009 -618 40 -24 82 -56 93 -70 27 -34 27 -102 0 -136 -11 -13 -106 -78 -212 -143 -106 -64 -201 -124 -210 -132 -16 -14 -18 -41 -18 -302 0 -291 2 -310 38 -310 16 0 267 148 610 359 180 111 270 173 310 213 216 217 215 574 -3 793 -37 38 -107 89 -185 136 -69 42 -253 154 -410 249 -434 264 -509 307 -563 326 -57 20 -191 17 -250 -6z"/>
5
- <path d="M1803 2994 c-10 -5 -13 -156 -13 -709 0 -671 1 -706 20 -767 27 -89 93 -184 167 -240 89 -67 157 -90 281 -96 92 -4 105 -2 117 14 12 16 14 134 15 735 0 669 -1 718 -17 737 -20 23 -514 322 -541 327 -9 2 -23 2 -29 -1z"/>
6
- </g>
7
- </g>
8
- </svg>
package/dist/features.html DELETED
@@ -1,133 +0,0 @@
1
- <!doctype html>
2
- <html lang="en">
3
- <head>
4
- <meta charset="utf-8" />
5
- <meta name="viewport" content="width=device-width, initial-scale=1" />
6
- <title>Pixcode Features - Claude Code, Codex, Cursor, Gemini, Qwen and OpenCode UI</title>
7
- <meta
8
- name="description"
9
- content="Pixcode feature overview: multi-CLI chat, files, shell, Git source control, changed file tracking, orchestration, provider models, API keys, Telegram notifications, MCP, plugins, themes, desktop installers, and Linux daemon mode."
10
- />
11
- <meta
12
- name="keywords"
13
- content="Pixcode features, Claude Code UI features, OpenAI Codex web UI, Cursor CLI dashboard, Gemini CLI web UI, OpenCode dashboard, Qwen Code UI, AI coding agent features, self-hosted AI developer tool"
14
- />
15
- <meta name="robots" content="index,follow,max-image-preview:large,max-snippet:-1" />
16
- <link rel="canonical" href="https://alicomert.github.io/pixcode/features.html" />
17
- <link rel="icon" href="favicon.png" />
18
- <link rel="stylesheet" href="site.css" />
19
- </head>
20
- <body>
21
- <nav class="site-nav" aria-label="Main navigation">
22
- <a class="brand" href="landing.html">
23
- <img src="logo.png" alt="" />
24
- <span>Pixcode</span>
25
- </a>
26
- <div class="nav-links">
27
- <a href="docs.html">Documentation</a>
28
- <a href="features.html">Features</a>
29
- <a href="orchestration.html">Orchestration</a>
30
- <a href="api-automation.html">API</a>
31
- <a href="https://github.com/alicomert/pixcode">GitHub</a>
32
- </div>
33
- </nav>
34
-
35
- <header class="hero docs-hero">
36
- <div>
37
- <div class="eyebrow">Feature map</div>
38
- <h1>Everything Pixcode brings into one workspace.</h1>
39
- <p class="lead">
40
- Pixcode combines AI coding CLIs, chat, file control, shell access, source control, orchestration, API automation, notifications, Telegram, MCP, plugins, themes, and desktop/server deployment.
41
- </p>
42
- </div>
43
- <div class="hero-summary">
44
- <strong>Product promise</strong>
45
- <p>
46
- Run agents, watch files, inspect commands, plan tasks, and automate the whole workspace without leaving your own machine.
47
- </p>
48
- <div class="chips tight">
49
- <span class="chip">Self-hosted</span>
50
- <span class="chip">API-first</span>
51
- <span class="chip">Task-aware</span>
52
- <span class="chip">Provider-neutral</span>
53
- </div>
54
- </div>
55
- </header>
56
-
57
- <main>
58
- <section class="section">
59
- <h2>Provider and model control</h2>
60
- <p class="sublead">
61
- 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.
62
- </p>
63
- <div class="grid three">
64
- <div class="card"><strong>Claude Code</strong><p>Use Claude Code sessions, tool output, notifications, and MCP-aware workflows from the Pixcode interface.</p></div>
65
- <div class="card"><strong>OpenAI Codex</strong><p>Run Codex-backed coding tasks, reviews, and one-shot automation through chat or REST API.</p></div>
66
- <div class="card"><strong>Cursor CLI</strong><p>Bring Cursor CLI into the same project workspace as the rest of your providers.</p></div>
67
- <div class="card"><strong>Gemini CLI</strong><p>Use Gemini CLI for Google model workflows without leaving Pixcode.</p></div>
68
- <div class="card"><strong>Qwen Code</strong><p>Manage Qwen-based coding sessions alongside other agents.</p></div>
69
- <div class="card"><strong>OpenCode</strong><p>Select OpenCode models and use OpenCode as a first-class worker in orchestration.</p></div>
70
- </div>
71
- </section>
72
-
73
- <section class="section alt">
74
- <h2>Workspace features</h2>
75
- <div class="grid three">
76
- <div class="card"><strong>Chat and sessions</strong><p>Project-aware sessions, provider selection, mode handling, slash command support, and structured tool rendering.</p></div>
77
- <div class="card"><strong>Fixed prompt composer</strong><p>The main input stays at the bottom of chat/project views so the screen behaves like a real messaging workspace.</p></div>
78
- <div class="card"><strong>Processing visibility</strong><p>The UI is designed to show when an agent is thinking, running, waiting, or returning output.</p></div>
79
- <div class="card"><strong>Files panel</strong><p>Browse, open, edit, upload, rename, delete, and inspect files without leaving the agent workflow.</p></div>
80
- <div class="card"><strong>Shell panel</strong><p>Open the project shell as split view or full view on desktop; use mobile-safe panel behavior on small screens.</p></div>
81
- <div class="card"><strong>Source Control</strong><p>Review Git status, changed files, diffs, branches, commits, and repository actions.</p></div>
82
- </div>
83
- </section>
84
-
85
- <section class="section warm">
86
- <h2>Control and automation features</h2>
87
- <div class="grid two">
88
- <div class="panel">
89
- <h3>Changed files Command Center</h3>
90
- <p>Tracks local working-tree changes, highlights newly edited files, and opens relevant paths so users can see what an agent changed immediately.</p>
91
- </div>
92
- <div class="panel">
93
- <h3>Multi-agent orchestration</h3>
94
- <p>Coordinates multiple agents with roles, labels, instructions, model choices, fallback providers, workflow previews, streaming events, and cancellation.</p>
95
- </div>
96
- <div class="panel">
97
- <h3>API access</h3>
98
- <p>External automation can use `px_` API keys for project access, agent runs, orchestration preview/run flows, and integration scripts.</p>
99
- </div>
100
- <div class="panel">
101
- <h3>Notifications</h3>
102
- <p>Browser push and Telegram notifications help long-running sessions report completion, failure, or action-required states.</p>
103
- </div>
104
- <div class="panel">
105
- <h3>Orchestration</h3>
106
- <p>Pixcode coordinates background workflow, review, and verification tasks through project-aware CLI adapters.</p>
107
- </div>
108
- <div class="panel">
109
- <h3>Open-source readiness</h3>
110
- <p>The repository ships with README, LICENSE, contributing guide, code of conduct, security policy, issue templates, releases, screenshots, and static docs.</p>
111
- </div>
112
- </div>
113
- </section>
114
-
115
- <section class="section">
116
- <h2>Designed for real working loops.</h2>
117
- <p class="sublead">
118
- 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.
119
- </p>
120
- <div class="flow-list">
121
- <div><strong>Prompt</strong><span>Send work to the provider that fits the task.</span></div>
122
- <div><strong>Observe</strong><span>See processing state, tool output, shell output, changed files, and orchestration steps.</span></div>
123
- <div><strong>Review</strong><span>Open changed files, inspect diffs, compare agent reports, and decide what ships.</span></div>
124
- <div><strong>Automate</strong><span>Use px_ API keys, Telegram, and orchestration workflows to keep work moving outside the browser.</span></div>
125
- </div>
126
- </section>
127
- </main>
128
-
129
- <footer class="footer">
130
- <strong>Pixcode features</strong> · <a href="docs.html">Documentation</a> · <a href="orchestration.html">Orchestration</a> · <a href="api-automation.html">API</a>
131
- </footer>
132
- </body>
133
- </html>
package/dist/generate-icons.js DELETED
@@ -1,49 +0,0 @@
1
- const fs = require('fs');
2
- const path = require('path');
3
-
4
- // Icon sizes needed
5
- const sizes = [72, 96, 128, 144, 152, 192, 384, 512];
6
-
7
- // SVG template function
8
- function createIconSVG(size) {
9
- const cornerRadius = Math.round(size * 0.25); // 25% corner radius
10
- const strokeWidth = Math.max(2, Math.round(size * 0.06)); // Scale stroke width
11
-
12
- // MessageSquare path scaled to size
13
- const padding = Math.round(size * 0.25);
14
- const iconSize = size - (padding * 2);
15
- const startX = padding;
16
- const startY = Math.round(padding * 0.7);
17
- const endX = startX + iconSize;
18
- const endY = startY + Math.round(iconSize * 0.6);
19
- const tailX = startX;
20
- const tailY = endY + Math.round(iconSize * 0.3);
21
-
22
- return `<svg width="${size}" height="${size}" viewBox="0 0 ${size} ${size}" fill="none" xmlns="http://www.w3.org/2000/svg">
23
- <!-- Background with rounded corners -->
24
- <rect width="${size}" height="${size}" rx="${cornerRadius}" fill="hsl(262.1 83.3% 57.8%)"/>
25
-
26
- <!-- MessageSquare icon -->
27
- <path d="M${startX} ${startY}C${startX} ${startY - 10} ${startX + 10} ${startY - 20} ${startX + 20} ${startY - 20}H${endX - 20}C${endX - 10} ${startY - 20} ${endX} ${startY - 10} ${endX} ${startY}V${endY - 20}C${endX} ${endY - 10} ${endX - 10} ${endY} ${endX - 20} ${endY}H${startX + Math.round(iconSize * 0.4)}L${tailX} ${tailY}V${startY}Z"
28
- stroke="white"
29
- stroke-width="${strokeWidth}"
30
- stroke-linecap="round"
31
- stroke-linejoin="round"
32
- fill="none"/>
33
- </svg>`;
34
- }
35
-
36
- // Generate SVG files for each size
37
- sizes.forEach(size => {
38
- const svgContent = createIconSVG(size);
39
- const filename = `icon-${size}x${size}.svg`;
40
- const filepath = path.join(__dirname, 'icons', filename);
41
-
42
- fs.writeFileSync(filepath, svgContent);
43
- console.log(`Created ${filename}`);
44
- });
45
-
46
- console.log('\nSVG icons created! To convert to PNG, you can use:');
47
- console.log('1. Online converter like cloudconvert.com');
48
- console.log('2. If you have ImageMagick: convert icon.svg icon.png');
49
- console.log('3. If you have Inkscape: inkscape --export-type=png icon.svg');