Repository navigation
v1.4.0 — People workspace, Ollama, native Windows
Bodhiorchard now works for the whole company, not just engineering. HR and Sales staff get a People workspace with leave, work from home, the team calendar and their own records, and never see the engineering side. This release also adds Ollama as a fourth AI provider, native Windows support, and a round of security fixes.
Highlights
- Leave and work from home. Balances per leave type, half days, optional holidays, and a request dialog that counts working days before anything is sent.
- Loss of pay. Leave past someone's balance goes through as unpaid days. The employee sees it before sending, the approver sees it before deciding, and the days are given back if the request is cancelled or a holiday is added.
- Approvals from Slack. Several reporting managers per person; any one of them decides and the first decision wins, with HR covering when no manager is left. Approvers get Approve and Reject buttons in a Slack DM.
- Leave policies per location. Leave types, quotas, working days, timezone, leave year, proration for new joiners and work-from-home rules per policy. Public holidays are imported by country and region, then edited.
- Offices and remote work. Each office follows a leave policy; remote people have no office and never show as working from home.
- Team calendar and daily Slack post. Names only, never the leave type or reason, and nobody on leave is @mentioned.
- Encrypted employee records. Bank and ID numbers and documents are encrypted with AES-256-GCM under a separate HR key. Reveals and downloads are logged, and each employee can see who opened their records.
- Workspace roles. New HR and Sales roles. People-only users are refused engineering routes at the API, MCP, WebSocket and multiplayer layers, and nobody can grant a role with more access than they hold.
- Ollama provider. Run the agents on a local or hosted Ollama endpoint, with no CLI and no data leaving your network.
- Native Windows. Hybrid mode runs on Windows without WSL, and scans work without Redis.
- Smaller additions. A two-player Backlash mini-game, file attachments on bug reports, restoring discarded BUDs from the board, uploading wireframe HTML as designs, BUD todos over MCP, and the latest Claude models as defaults.
Security
- Full Docker installs now generate their own
SECRET_KEY,ENCRYPTION_KEYand multiplayer bridge secret on first start and keep them on a volume. Stored tokens are re-encrypted off the old shared default key automatically, which signs everyone out once. - Deactivated users lose access straight away, and refresh tokens no longer work as access tokens.
- Request bodies are capped at 26 MB.
- Setup endpoints are closed once setup is done, and the directory picker is confined to the home directory.
Upgrading
- Migrations run on start as usual.
- Employee records have their own encryption key,
HR_ENCRYPTION_KEYS. Full Docker generates it on first start and keeps it on thesecrets_datavolume. The npx installer (now 1.1.0) adds it to.envon your nextbodhiorchard startorupdate, andnpm run setupadds it tobackend/.envfor Hybrid. Back it up with your data: records encrypted with it can't be read without it. - Production-mode installs (
docker-compose.prod.yml/deploy.sh) must setHR_ENCRYPTION_KEYSthemselves and refuse to start without it. Generate one withecho "k1:$(openssl rand -base64 32)". - Existing custom roles keep engineering access. Give HR staff the new HR role, and Sales or other non-engineering staff the Sales role.