Tools

Configure Flutter widget inspection, native tool suites, artifacts, and Dart custom tools behind a runtime tool guard.

Flutter combines framework tools registered in Dart with the standard native iOS and Android suites.

await Ansight.instance.initializeAndActivate(
  createOptionsBuilder()
      .withAnsightDefaults()
      .withReadOnlyToolAccess()
      .withRemoteTools(
        const AnsightRemoteToolsOptions(
          visualTree: true,
          database: AnsightDatabaseToolsOptions(),
        ),
      )
      .build(),
);
await AnsightFlutterInstrumentation.instance.install();

Guide	Purpose
VisualTree	Inspect Flutter and native UI sources, screenshots, and overlays.
Flutter Inspection	Query mounted widgets, diagnostics, search results, and navigation state.
Database	Discover SQLite files, schema, and read-only queries.
FileSystem	Inspect and transfer files in approved roots.
Preferences	Read or repair approved preference keys.
SecureStorage	Access explicitly allowed secure values.
Reflection	Inspect supported native roots.
Native Android JNI Reference Diagnostics	`jni_references.capture_graph` through native all-in-one defaults; there is no suite-specific Dart option.
Custom Tools	Expose narrow Dart operations.

All tools remain subject to AnsightToolGuard. Prefer read-only access and keep tool registration inside the app’s development guard.

Native catalog entries expose current availability, unmet state, remediation, and retryability through runtime, with a top-level executable flag. The native runtime rechecks availability immediately before execution. Dart-backed tools are considered available while registered because the Dart registration API does not currently expose a pre-invocation availability callback.