Skip to main content

miren detective

Debug with Workbench and read-only local source tools

Ask Workbench is a Miren Labs feature. Ask for access on Discord: https://miren.dev/discord

Ask the same cluster-scoped Workbench available in Miren Cloud. Requires a Cloud-registered cluster, a Cloud login, and Workbench enabled for the cluster's organization. Cluster selection follows the usual --cluster, MIREN_CLUSTER, per-app state, and active-cluster rules.

With no question, starts an interactive conversation; piped input is treated as one question. Defaults to the app in the current directory or a parent directory, or in -d when specified. Pass -a or MIREN_APP to override the app. Outside an app directory, asks about the cluster. Terminal responses render Markdown with a waiting indicator; redirected responses stream as plain text. Local tool calls are shown as they happen. Ctrl-C aborts any active response and exits the CLI; it does not return to the chat prompt. Use /quit or Ctrl-D to exit interactive chat normally.

Cloud write requests show their summary, arguments, and consequences for approval in the terminal, including when a positional question is supplied. Use arrow keys and Enter to allow once, allow for this conversation, or deny (the default). Chat text and pasted text never grant permission. Inline approval requires terminal input and output; otherwise writes remain gated and Cloud's browser link is displayed.

Detective enables read-only tools for listing, reading and searching source in the current directory (or -d). Use --no-local-tools to ask about the cluster without exposing local source files. Requested file content is sent to Miren Cloud. There is no model-callable local shell or editing. In a Git repository, Git must be installed to resolve .git/info/exclude and the effective global excludes file, including included config and worktrees; failures refuse source access. Symlinks, gitignored files, most hidden paths, and common credential files are excluded; .miren/app.toml is eligible unless gitignored. These exclusions are not secret detection: choose a source-only directory and keep sensitive files out of it.

Local tools require the Cloud client-tool bridge. An unavailable bridge is an error, not a fallback that uploads your tree. Tools exist only while this CLI is connected; each invocation starts a new conversation.

Usage​

miren detective [args...] [flags]

Flags​

  • --app, -a — Application to focus on (defaults to the local app, if any)
  • --cluster, -C — Cluster name
  • --config — Path to the config file
  • --dir, -d — Local source root (default: .)
  • --identity, -i — Cloud identity (defaults to the cluster's identity)
  • --no-local-tools — Disable local source access; ask about the cluster without sharing local files

Global Options​

  • --options — Path to file containing options
  • --server-address — Server address to connect to (default: 127.0.0.1:8443)
  • --verbose, -v — Enable verbose output

Examples​

Interactive chat:

miren detective -C production

Ask about the cluster without local source:

miren detective -C production --no-local-tools "Is the cluster healthy?"

Inspect an app's source:

miren detective -C production -a myapp -d ./myapp "Why does startup fail?"