OpenOri automatically scans your workspace directories and builds a rich understanding of your projects. It knows you’re in a “React + TypeScript + Vite project” before you tell it.Documentation Index
Fetch the complete documentation index at: https://docs.openori.dev/llms.txt
Use this file to discover all available pages before exploring further.
What OpenOri detects
| Signal | How it’s detected |
|---|---|
| Languages | File extensions (.ts, .py, .rs, .go) |
| Frameworks | Config files (next.config.js, vite.config.ts, Cargo.toml) |
| Package managers | package.json, requirements.txt, go.mod, Cargo.lock |
| Build tools | tsconfig.json, webpack.config, Makefile |
| Structure | Directory layout, monorepo detection |
How it helps
When project context is active, OpenOri tailors its responses:- Uses the right language and framework conventions
- Suggests project-specific patterns
- Knows relative file paths
- Understands your dependency versions
“Help me add a route” → Generic Express.js exampleWith project awareness:
“Help me add a route” → Next.js App Router example using your project’s conventions, file structure, and TypeScript config
Workspace scanning
OpenOri scans common project directories on your machine:~/projects/,~/code/,~/dev/,~/repos/~/Documents/,~/Desktop/(for one-off projects)- Any directory you’ve opened in your editor
~/.ori/context/projects/ and refreshed periodically.
Project scanning is read-only. OpenOri examines config files and directory structure — it never modifies your projects during scanning.