doc.haus

A local legal-document workspace built on OpenCode. Upload documents into matters, ask source-grounded questions, and prepare drafts and redlines for lawyer review. Generated work requires professional review.

Start locally

Install Git, clone this repository, then run:

git clone https://github.com/sure-scale/doc-haus.git
cd doc-haus
./start.sh

The launcher checks for Bun 1.4.0 or newer and the document tools (Deno 2, Python 3.10+, markitdown, Poppler, Tesseract, LibreOffice Writer and the Carlito font). It lists anything missing or out of date and offers to install it; press Enter to accept. macOS uses Homebrew (offered first if absent); Linux uses apt-get, dnf or pacman. The launcher then installs frozen dependencies and opens the web app at http://localhost:5174. It runs engine, ingest and web on separate local ports. A new installation needs no credentials to boot. Accept the launch notice, choose a provider (detected options appear first), connect with its offered sign-in method and detected defaults, then confirm primary/fast models in setup. Research and firm or jurisdiction details are optional. Opening setup does not make a paid model request; connection tests run only when requested. Provider access and quota remain subject to the provider's account and organization policies.

Only Bun is required, and the launcher installs it. The stack starts without declined tools, and a declined set is not offered again until another tool goes missing. The container includes every tool. See setup.

Local container

docker compose up --build

Open http://localhost:5173. Only web is published, on host loopback. Engine and ingest stay on container loopback behind /engine and /ingest proxies. Named workspace and runtime volumes retain documents, native credentials, sessions and settings across recreation. This is a local self-host configuration. Internet-facing or team hosting needs a separate deployment design.

Settings, data and updates

Saving settings leaves the shipped dochaus/opencode.json unchanged. User model and provider options and agent/skill toggles live in runtime configuration; credentials use native storage. Custom builder definitions have separate backup requirements described in the storage guide. See storage and backup and upgrades, including the explicit migration path for older installations with tracked settings.

Detailed provider/tool captures are off by default. Troubleshooting capture requires DOCHAUS_PROVIDER_CAPTURE_DIR set to a private absolute directory; DOCHAUS_PROVIDER_CAPTURE_DIR=off disables it without deleting prior captures. Captures can contain confidential document and model content. Ordinary native sessions and sanitized failure diagnostics remain durable independently.

Contributing · Security · Licensing · Attribution

The root install script belongs to upstream OpenCode. Use start.sh for doc.haus.