Skip to main content
Graphify Local reads its per-run settings from environment variables. Set them in your shell, CI job, or MCP client config. Nothing here is needed for a code-only build; you reach for these when you change the output folder, tune model calls, or quiet the hooks.
Use environment variables when a setting depends on the machine or the run (a CI output path, a model name, a timeout). For settings that describe the repository itself, use .graphifyrc.

How it works

Command-line flags win over environment variables, and environment variables win over built-in defaults. Several flags simply set the matching variable for the rest of the run: --api-timeout sets GRAPHIFY_API_TIMEOUT and --max-workers sets GRAPHIFY_MAX_WORKERS. Boolean variables accept 1, true, or yes. Provider keys such as ANTHROPIC_API_KEY are covered on LLM providers.

Output and size

Model calls

Ollama

Media

Hooks and the agent loop

Server, logs, and output

Query logging is off unless you turn it on. Graphify Local sends no telemetry.

See it in action

Verify and troubleshoot

To list every variable your installed version reads:

What’s next

LLM providers

Keys, defaults, and custom endpoints for each backend.

CLI reference

Every command and flag.

Try it in Graphify

We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.