Nam Pham Dinh ThanhandClaude Opus 5
d37a0c1578
The rail was setFixedWidth, so the handle QSplitter draws between it and the content was inert — it looked draggable and did nothing when dragged. The expanded rail is now a range (132–360px) instead of one number, so the handle has something to give. Collapsing still pins it at 54px exactly, and a width dragged to is remembered across the fold rather than snapping back to the 150px default. Long project names and RECENTS threads are what a wider rail buys. check_rail_resize drives the splitter the way the handle does and asserts the rail follows, clamps at both ends, folds to 54px and comes back to the chosen width. Restoring setFixedWidth fails it — the first attempt at that mutation passed, because setMaximumWidth on the next line quietly undid it. 16/16 checkers pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Cowork Local
Cowork Local is the internal AI cowork desktop platform owned by the Cowork Team. It provides the Cowork runtime, workspace and agent experiences, MCP/connectors, security controls, and model routing foundation.
The Cowork Team owns this product and its stable branch. The FSG AI Core Team contributes selected reusable capabilities through branches and Pull Requests; it is not the owner or final merger of this repository.
Quick start
The imported application is a Python/PySide6 package. Run it from the directory that contains cowork_local:
python -m cowork_local
The source snapshot does not include a complete runtime dependency manifest. Use the Cowork Team's supported runtime environment until that packaging contract is documented. The reliable automated test surface currently checked by CI is:
python -m pip install -r cowork_local/requirements-test.txt
python -m pytest cowork_local/tests -q
When already inside this repository, run python -m pytest tests -q.
Configuration and runtime data live under ~/.cowork_local/. Provider keys and local unlock codes must be supplied through environment variables or an approved secret manager; see .env.example.
Contributing
Start with START_CONTRIBUTING.md, then read CONTRIBUTING.md. Core AI task execution remains in fsg-ai-core-assets; source changes are reviewed as Pull Requests in this repository.
Security concerns should follow SECURITY.md. Ownership and completion rules are documented under docs/governance/.