oak.space valid

Oak

Oak is the agentic substrate for software development: the version-control and storage layer autonomous coding agents build on. Mount remote repositories without a full clone, run a branch per task in parallel, snapshot up to 95% faster than git, and skip the per-commit message tax. Bring your own agent (Claude Code, Codex, Cursor): Oak is the version control system those agents push to, and it makes no AI calls of its own.

For agents: Version-control system for coding agents (Claude Code, Codex, Cursor): lazy repo mounts, parallel branches per task, faster snapshots than git. Docs include Mar

version controlgit alternativecoding agentslazy mountsagent workflows

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:39:37.553Z. Cached copy · Source on oak.space

# Oak

> Oak is the agentic substrate for software development: the version-control and storage layer autonomous coding agents build on. Mount remote repositories without a full clone, run a branch per task in parallel, snapshot up to 95% faster than git, and skip the per-commit message tax. Bring your own agent (Claude Code, Codex, Cursor): Oak is the version control system those agents push to, and it makes no AI calls of its own.

Oak keeps a familiar surface — repos, branches, PR-style merges, push/pull, webhooks, large-file support — on a Rust engine with content-addressed storage, content-defined chunking (BLAKE3 + FastCDC), and lazy filesystem mounts. It is designed for how agents actually work: high branch volume, constant snapshots, parallel sessions, and large files.

## Key facts

- Install: `curl -fsSL https://oak.space/install | sh` (macOS, Linux) or `irm https://oak.space/install.ps1 | iex` (Windows PowerShell), then `oak login` and `oak init`. Or hand your agent the prompt from the homepage install section **"Copy prompt"** button (full setup + docs; not the install-only Copy button) and let it install itself.
- Platforms: macOS (Apple Silicon and Intel), Linux (x86_64), and Windows (x86_64). Lazy mounts use FSKit on macOS, FUSE on Linux, and ProjFS on Windows. Linux ARM64 binaries are published on the GitHub releases page but the installer does not select them yet.
- Pricing: Oak is free while it is in beta. Every organization gets 100GB of storage, with unlimited repositories, open branches, and organization members. Paid plans will return later; email zach@oak.space if you need more than 100GB in the meantime.
- Branch model: you always work on a feature branch locally; `main` exists only on the server; `oak merge` is a server-side squash; intermediate commits carry no message; the branch description is the source of truth and becomes the squash-commit message.
- CI: Oak runs CI on your own machines. Register them as self-hosted runners (the stock open-source `gitea-runner`) under an organization's Settings → Runners; workflows live at `.oak/workflows/<name>.yml` in GitHub Actions syntax (`runs-on` names runner labels; `needs:`, static matrices, `uses:` actions, and expressions work) and fire on branch pushes and merges (`push`, `pull_request`) or manually (`workflow_dispatch`). Per-repo CI secrets are encrypted at rest and masked in logs. CI is the merge gate: a squash-merge onto main is refused while the branch head's CI is red or in flight; `oak merge --wait` rides it out and `oak merge --force` overrides it.
- Path permissions: declared in the repo as `.oak/PERMISSIONS` (CODEOWNERS-shaped, read from the `main` tip, last matching entry wins). Principals are `@user`, `@group/slug`, `*` (every repo reader), `@public` (the world), or none (org owners/admins only). For a repo reader the file narrows — restricted file names and sizes stay visible while their bytes are withheld. For an outsider `@public` widens instead, so a privat
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=oak.space · GET /v1/domain/oak.space · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for oak.space:
1. POST https://agentwebmap.com/v1/sites/oak.space/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://oak.space/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/oak.space/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/oak.space).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.