Custos wires Grok into LegalOS

Custos's fork bolts on xAI's Grok as a third AI engine and adds another cloud-storage option behind it.

integrationinfrastructure

Custos has forked Mike under the name LegalOS and given users a new brain to pick from: Grok, the model built by Elon Musk's xAI. It sits alongside the Claude and Gemini options already in the codebase, so a firm can now route its legal chat through whichever of the three it trusts most. Custos also added Supabase Storage - a cloud file-storage service - as a supported place to keep documents, next to the existing option.

One wrinkle worth knowing before you lean on it: the model picker always shows Grok as available, even when no Grok credentials are set up. Users won't find out it isn't wired up until a request actually fails, rather than being warned up front on the selection screen.

So what Legal-ops leads weighing which AI vendor to standardise on should note LegalOS now keeps Grok, Claude and Gemini all on the table.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from Custos/legalos, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`6ee8547e`	Fork as legalos: xAI Grok support, Supabase S3, and bugfixes	Custos	2026-05-04	↗ GitHub
commit body - Add xAI provider (grok-4.3) with OpenAI-compatible streaming + tool calling - Add model dropdown to TabularReviewView header (persists tabular_model preference) - Patch storage.ts for Supabase S3 (region from env, forcePathStyle) - Fix GET /projects 500: jsonb contains needs JSON-stringified array - Update README with attribution to upstream willchen96/mike under AGPL-3.0
`d9295771`	Per-user xAI API keys	Custos	2026-05-04	↗ GitHub
commit body - New user_profiles.xai_api_key column. - userSettings reads/returns xai key alongside claude + gemini. - UserProfileContext exposes xaiApiKey + updateApiKey('xai', ...). - Account → Models page renders an xAI key field. - Tabular review xAI dropdown stays available without a per-user key (env XAI_API_KEY remains the fallback) but a user key takes precedence.

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-45.md from inside the repo you want the changes in.

⬇ Download capture-thread-45.md