Tellagen
← Back to Support Center

Run a local Diagnosis for an incident

Use a local client, such as Codex or Claude, with an MCP server that connects it to Tellagen. Then run an incident Diagnosis and review the saved result.

GuideLast verified Open Markdown version
On this page

Before you start

Intended audience

Incident commanders and responders who investigate an active incident.

Required permissions

You need an active responder seat. The Local Diagnosis preset includes incidents:read, incidents:write, slack_context:read, services:read, teams:read, and custom_fields:read.

Prerequisites

  • Install Codex CLI or Claude Code on the computer that will run the investigation.
  • Sign in to the correct Tellagen workspace.
  • A local client is Codex or Claude running on your computer.
  • An MCP server lets the local client call Tellagen or a provider tool.
  • A provider tool gives the client read-only access to an evidence source, such as monitoring or infrastructure.
  • Already configured? Start at Check local setup.

Procedure

Prepare the client

  1. Step 1 of 13

    Open local investigation tools

    Open Settings. The navigation label is Local investigation tools. The page heading is AI diagnostics.

  2. Step 2 of 13

    Choose a client

    Select Codex or Claude. Tellagen shows instructions for that client.

    Local investigation tools page with the three client setup steps.
    Choose a client before you copy its setup command. Open full-size image(opens in a new tab)

  3. Step 3 of 13

    Create the API key

    Create a key with the Local Diagnosis preset. Store the token immediately because Tellagen shows it once.

    API key form with the Local Diagnosis preset and its scopes.
    The preset supplies the scopes needed by a local Diagnosis run. Open full-size image(opens in a new tab)

  4. Step 4 of 13

    Copy the Tellagen command

    Find the Tellagen MCP card. Select Copy.

    Tellagen MCP setup card with its client install command and Copy action.
    Copy the Tellagen MCP command for the selected local client. Open full-size image(opens in a new tab)

  5. Step 5 of 13

    Add required provider tools

    Add only the provider MCP tools that the investigation needs. Keep their credentials in your local client.

  6. Step 6 of 13

    Check local setup

    Select Check MCP tools. Paste the generated diagnostic prompt into your local client.

    Codex configuration check

    shell
    codex mcp list

    Claude configuration check

    shell
    claude mcp list
claude mcp get tellagen

  7. Step 7 of 13

    Review the setup result

    Return to Tellagen. Make sure that required cards show INSTALLED and ACCESS OK. Review each stale result before use.

Run the investigation

  1. Step 8 of 13

    Open Diagnosis

    Open the incident. Select Diagnosis.

  2. Step 9 of 13

    Choose the run relationship

    Select New independent run for a separate investigation. Select Follow up on this run to continue the selected result.

  3. Step 10 of 13

    Set the focus

    Enter one focused question. Include the failed behavior, relevant service, and time window.

  4. Step 11 of 13

    Choose evidence

    Open Evidence options. Enable Include incident Slack context only when the channel context is necessary.

  5. Step 12 of 13

    Start the handoff

    Select Run diagnosis. Copy the start command into your local client. Tellagen shows the run as waiting for local work.

Review the result

  1. Step 13 of 13

    Review the saved result

    Review Investigation result, Evidence and checks, Run details, and Raw local tool trace. Separate observed evidence from suggestions.

You are done when…

Tellagen stores the local run, checked evidence, findings, and trace on the incident.

Troubleshooting

The page says No diagnostic tools are available for this client.

Choose the client you installed, then copy and run the matching command from the MCP tool gallery.

Codex shows Auth: Unsupported for the local connection.

This status is expected for this local connection. Tellagen authentication uses TELLAGEN_API_KEY in the local MCP configuration.

Run diagnosis is not available after setup.

Confirm that the Local Diagnosis API key was created from the preset, that its owner has an active responder seat, and that the Tellagen MCP connection uses that key.

Diagnosis ended early or is inconclusive.

Review Tool activity and the missing evidence in the Diagnosis tab. Fix the local tool or credential setup, then run a new diagnosis or a follow-up diagnosis.

A required tool does not show INSTALLED.

Run the install command for the selected client. Then run Check MCP tools again.

A tool shows a stale result.

Run the generated diagnostic prompt again. Use the result only after its status is current.

The local client cannot call Tellagen.

The incident record and saved investigation results stay in Tellagen. Make sure that the key uses the Local Diagnosis preset and that the workspace URL is correct. Run Check MCP tools again. If access still fails, ask a workspace settings administrator to review the key and local setup. Then email Tellagen support.

Related articles

External setup references