Skip to main content
The workspace is a git folder of Markdown — knowledge, plans, and the agent’s session, all just files. The knowledge itself follows an open standard (OKF, below). Every workspace route derives your identity from the API key; you never pass a subject.

​
Browse and read

Pass hidden=true to tree to include dotfiles. git is the durable state and the undo — every agent write is a commit.

​
The knowledge graph is an OKF bundle

The kg/ subtree follows the Open Knowledge Format (OKF) v0.1 — Google’s open, vendor-neutral standard for markdown knowledge. Each entity is one file at kg/entities/<type>/<slug>.md with YAML frontmatter:
Vexa’s frontmatter contract (type/id/title required, per the workspace.v1 schema) is a strict superset of OKF, which requires only type — so every workspace is a conformant bundle any OKF consumer can read, and [[wikilinks]] are a tolerated extension. Two reserved filenames carry no frontmatter and are not entities:
  • index.md — a per-directory listing (- [Title](file.md) — description) for progressive disclosure; seeded workspaces ship them generated, and the agent maintains them as entities are added or removed.
  • log.md — optional change history, newest first, grouped under ## YYYY-MM-DD headings.
Because the bundle is just files in git, it is portable by construction: tree + file above read it over the API, and a git clone (or the swap endpoint below) moves the whole knowledge base between tools — nothing about it is Vexa-specific.

​
Upload documents

Add files to the workspace so agents can ground on them (multipart; ≤25 MB each):

​
Initialize a fresh workspace

Idempotent — seeds the workspace if it doesn’t exist yet:

​
Attach your own git repo

Swap in an external git repo as the active workspace — the current one is parked, not lost:
Omit repo to swap back to the seed workspace. Check what’s attached:

​
Next

Put an agent to work on what’s here — chat with the workspace or run an unattended routine over it.