Skip to main content
Version: 1.0.0

Explore a Touba project

The explorer provides a graphical view of resources, flows and authority declared in your code. Use it to understand a project, review a change and locate the source of a relationship, including code written with an assistant.

Open the explorer​

From your project directory:

touba explore

Your browser opens a local address. Keep the terminal open; Ctrl+C closes the service. In VS Code, run Touba: Explore Project. The context menu of a .tb file offers Touba: View in Graph to select the element at the cursor.

Choose a view​

ViewContentsUseful question
ArchitectureModules, packages, declarations, imports and source callsWhat makes up this project?
FlowEntries, calls, conditions, loops, approvals, parallel operations and recoveryHow is this process organized?
GovernanceResponsibilities, uses, callable_by, memory access, capabilities and required secret namesWhat authority does the program declare?

Each arrow names its relationship. May use represents uses; may invoke agent represents callable_by. A call written in source appears in Architecture and Flow. Execution traces describe the decisions made during a run.

A parallel operation shows its target, max_concurrency and max_items. The actual branch count depends on the input list at runtime; the join returns results in input order.

  1. Select a grouped module or package and choose Explore contents.
  2. Search by name or filter by kind, module and package.
  3. Select a resource to read its signature, responsibility, constraints and relationships.
  4. Use Focus and Depth to follow incoming or outgoing relationships.
  5. Choose Open source to reach the code in VS Code or read the snapshot in your browser.

The resource list supports keyboard navigation. The graph includes zoom, pan, fit and SVG or PNG export. French and English interfaces share the same views in light and dark themes.

Module details display budgets directly: maximum calls, invocations and steps, along with the allowed duration. Grouped cards show how many resources they represent. Individual module and type cards keep their plain kind label.

Adjust the display​

The Display button controls how the graph is drawn. Your choices are kept:

  • Relationship labels: always visible, only around the selection, or hidden;
  • Orientation: vertical or horizontal;
  • Density: comfortable or compact.

The resources and details panels can be hidden to enlarge the graph. Keyboard shortcuts: [ for resources, ] for details, \ for the graph only, 0 to fit, + and - to zoom, Esc to clear the selection. Clicking the selected resource again, or Reset, clears the selection and shows the whole graph again. The mouse wheel zooms around the pointer; double-clicking the background fits the graph.

Refresh​

Saved files are analyzed automatically. Selection and viewport are preserved. Compilation errors display diagnostics and, when available, the last valid graph with a showing the last valid graph notice. Its source remains the compiled snapshot.

Analysis uses .tb files and registered package metadata. Tools appear as contracts for their JavaScript or Python handlers. Opening the explorer compiles the project in read-only mode without running business operations.

Local access and project size​

The service listens only on 127.0.0.1. The printed address contains a temporary access key for this project. Close the terminal to close access. Secret values are not loaded from the secret manager, and .env files are not read.

Analysis is bounded to 512 sources, 8 MiB total and 1 MiB per file. Views with more than 200 nodes keep the complete resource list and ask you to refine the filters. Source paths must stay inside the project; symbolic links are refused. Packages use the same integrity checks as the project commands.

To select a port or open the browser yourself:

touba explore . --port 4180 --no-open

Continue with the guided tutorial and the CLI reference.

Read the details​

ResourceDisplayed information
ModuleBudgets and declared project entry points
ConstantType and value, including civil dates
TypeFields, constraints and defaults
Call or conditionNamed arguments and readable expression
ApprovalContext, role, deadline and signer rule
PackageVersion, publisher, license, exports, dependencies and host modules

Nested structures are displayed as fields. Source references support Open source. Values calculated during a run remain available in its traces.