Developers and small agencies

Your next code change, with context.

An unfamiliar project. A stubborn bug. A delivery that cannot wait. Start with a bounded task, not a sweeping promise.

Start with Theus CLI Try a task in the browser

The CLI works in the folder you open. In the browser, supply the context you want to share. No button in this guide sends a message for you.

Three tasks to try in your project.

These are instructions to try, not generated answers or success stories. Results depend on your project, model and available tools.

Understand before editing.

Explore an inherited repository without guessing where things live.

Instruction for Theus

Explore this project without modifying files. Locate entry points, configuration and the path of a request. Use the Ñaupa graph if available and check that the index matches the current code. Cite paths and symbols you actually read. Separate facts, inferences and unknowns.

What to check before calling it finished

Paths exist, the flow cites code and the report identifies gaps. Do not accept a convincing map without sources.

Scope a real bug.

Fix an issue without rewriting the project.

Instruction for Theus

I will describe a bug and its expected behavior. First identify a minimal reproduction and related functions. Propose the smallest change, its risks and a test that would demonstrate it works. Do not edit or run tests before I approve the scope. Do not read secrets or change production configuration.

What to check before calling it finished

There is a reproducible case and a concrete check. The approved change resolves it without hiding failures or adding unrelated work.

Deliver with evidence.

Explain the change and leave a clear next session.

Instruction for Theus

Summarize the change we just worked on: affected files, rationale, tests actually run and their results, risks and remaining work. Do not present proposed tests as passed tests. End with one concrete task to resume. Do not publish or send anything to third parties.

What to check before calling it finished

The summary matches the changes and actual outputs. Pending checks remain explicitly pending.

Ñaupa: ask the code, get references.

With Ñaupa installed and the project indexed, Theus can query symbols and relationships through MCP. A graph helps locate code; it does not replace checking that the index is current.

search_graph: find functions and classes.
trace_path: follow calls and dependencies.
get_code_snippet: read a located symbol.

Install and use Ñaupa MCP

Tomorrow, resume the same work.

Before closing, ask for a summary and a next task. To continue a CLI conversation, open the same project folder and run:

theus -c

Review changes since the last session before authorizing new actions. Memory does not replace the current state of your files.

The index lives on your machine. That does not make every session offline: context sent to a remote model leaves your machine. Do not include credentials or client files without permission.

Before you start

Is this a real customer demonstration?

No. This guide contains reproducible tasks and review criteria. We do not present undocumented results, savings or testimonials.

Must I share my entire repository?

Not to try a task. Start with an example project or a snippet you are authorized to share. Review the provider and context before using private code.

Can I pay without contacting sales?

The pricing page shows available self-service options. Your account displays the plan and quota activated by the server. Returning from checkout is not a payment receipt.

First, a result you can check.

Then choose a plan based on actual use. Current quotas, currencies and terms are on the pricing page. No sales call required.

See plans and limits Open documentation