Get Started — Undes

Step 1

Requirements

For the MVP, Undes Community is distributed as a public Node.js-based developer tool. Pro uses a separate licensed package and requires package access after purchase. Team and Enterprise usage is discussed directly and does not have a public install path yet.

Node.js Use a recent LTS or current version supported by the package.

npm Used to install the Community CLI and update the package.

npm package access Community is public. Pro requires licensed package access.

AI provider key BYOK: OpenAI, Anthropic or Google for Community. Expanded providers and local models belong to Pro when shipped.

Repository access Run Undes inside the project you want to analyze.

License account Required only for paid licensed usage.

Step 2

Install Undes

Start with the Community package. It is the public package intended for first tests, local experiments, and validating whether the Undes workflow fits your engineering process.

Community Public package

Use this package to run Undes with your own AI provider keys and generate reviewable operator-facing result artifacts.

Terminal

npm install -g @undes.ai/cli

Check installation

undes --version

Pro Licensed package

Pro uses a separate licensed package. After purchase, the install command, license activation instructions, and package access details will be available in your account. Pro is also the paid track for expanded LLM providers, local model servers, run history and richer inspection.

View Pro plan

Team / Enterprise Discuss separately

Organization usage does not have a public self-service package, install command, or activation path yet. Contact us if you need to discuss scope.

Contact us

Step 3

Configure your AI provider keys

Undes is BYOK-first. You keep model billing, provider configuration and data handling under your own AI provider account.

.ai.env

OPENAI_API_KEY=your_openai_key
CLAUDE_API_KEY=your_claude_key
GEMINI_API_KEY=your_gemini_key

You do not need every provider for the first run. Start with the provider you already use, then add more first-party providers when you want stronger cross-model review.

Provider scope: Community supports OpenAI, Anthropic and Google. OpenRouter, NVIDIA NIM, generic OpenAI-compatible endpoints, Ollama, LM Studio and llama.cpp belong to the Pro provider-expansion track when available in the licensed package.

Step 4

Run your first analysis

Start with a small real task. Avoid toy prompts. A good first run is a bug investigation, a risky refactoring, or a pull request that needs a second opinion.

Terminal

cd your-project

undes run "Analyze the authentication flow and identify risky assumptions before refactoring."

Good first prompt: ask Undes to verify a concrete engineering concern, not to generate generic advice.

Step 5

Read the generated artifacts

Undes is designed to produce reviewable engineering output. The final artifact should make it clear what was checked, what was assumed, which hypotheses were rejected, and what still needs validation.

Decision The recommended engineering conclusion or next action.

Evidence Files, logs, facts, snippets and observations used by the agents.

Rejected hypotheses Alternative explanations that were considered and ruled out.

Open checks Tests, risks or missing evidence that still require human review.

Optional

Use Undes in CI/CD

Undes is not optimized for instant chat-style answers. Some runs may take longer because the process includes multiple agents, critique and consensus. That makes it suitable for background checks, scheduled analysis, or CI/CD workflows.

CI example

undes run "Review this pull request for risky assumptions, missing tests, and unsafe architectural changes."

For organization-wide CI/CD usage, contact us first so the scope can be discussed directly.

Help

Troubleshooting

The command is not found

Check that the package was installed globally and that your npm global bin directory is included in your PATH.

The provider returns authentication errors

Check your API key, provider account status, model access, rate limits and billing settings.

I cannot install a paid package

Pro is not installed from the public Community package. Use the licensed package instructions from your Undes account after purchase. Team and Enterprise install paths are not public yet.

The run takes a long time

This can be expected. Undes favors verification depth over instant response speed. Use smaller prompts or narrower repository scope for faster runs.

The result is too broad

Ask a more specific engineering question. Include the subsystem, expected risk, relevant files, or decision you want reviewed.

Run your first Undes analysis on a real engineering task.