For the complete documentation index, see llms.txt. This page is also available as Markdown.

Targets

Inspect targets, goals, and run history for a deployment.

Targets are deploy-specific views of your application. Each target usually maps to a commit, branch, preview environment, or production deploy.

There is no separate Targets page.

Open a product, then use the target menu in the top-right navbar, next to the active product, to create or switch targets.

Create a target

After you create a product, create a target for the deployment you want to test.

Each target includes:

  • URL: The deployment URL Duku explores

  • Version: A commit SHA, build ID, or release identifier

  • Metadata: Optional context like branch name, PR number, or commit message

Target detail

With a target selected, open Exploration to inspect:

  • Merged state graph: The aggregate graph across explorations for that target

  • Discovered pages: Every state found so far

  • Identified goals: Business-critical destinations extracted from the graph

  • Runs table: Exploration and intent runs for that target

Open Schedules to automate recurring runs for the target.

From there, you can start new explorations or intent tests. Each exploration starts from the target URL.

The target graph improves as Duku accumulates more exploration data for the same deployment.

Last updated