| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| Pixcode-1.33.9-amd64.deb | 2026-04-27 | 179.1 MB | |
| Pixcode-1.33.9-arm64.dmg | 2026-04-27 | 202.5 MB | |
| Pixcode-1.33.9-x64.dmg | 2026-04-27 | 207.1 MB | |
| Pixcode-1.33.9-x86_64.AppImage | 2026-04-27 | 235.2 MB | |
| Pixcode-Setup-1.33.9.exe | 2026-04-27 | 172.1 MB | |
| Pixcode v1.33.9 -- Fix OpenCode_Qwen routing from geminiSessions pool source code.tar.gz | 2026-04-27 | 2.4 MB | |
| Pixcode v1.33.9 -- Fix OpenCode_Qwen routing from geminiSessions pool source code.zip | 2026-04-27 | 2.8 MB | |
| README.md | 2026-04-27 | 778 Bytes | |
| Totals: 8 Items | 1.0 GB | 0 | |
Bug Fixes
- fix: opencode sessions stored in
geminiSessionspool (common because OpenCode is a Gemini-CLI fork and sessions land in~/.gemini/tmp/) were being tagged as__provider: 'gemini'in the session-resolution effect, causing all messages to route to Gemini CLI instead of OpenCode CLI - fix (v1.33.8): streaming handler used stale frontend provider state instead of the message's actual provider field
Root Cause
The sidebar correctly detected and re-tagged OpenCode sessions from the Gemini pool, but the useProjectsState session-resolution effect only had Qwen detection — OpenCode sessions found in geminiSessions were tagged as Gemini, so every message was sent as gemini-command.
npm: npm i -g @pixelbyte-software/pixcode@1.33.9