temporal-troubleshooting

temporal-troubleshooting is an agent for Claude Code from nodnarbnitram/claude-code-extensions. It costs 38 tokens per session (3,315 once invoked), scanned A, original, MIT.

A troubleshooting specialist for Temporal.io, a platform for running reliable workflows, across its supported programming-language SDKs.

In plain words
What is it for?
Use it to investigate Temporal errors and production incidents using logs, workflow history, web-console details, and validation steps.
Why use it?
It helps trace failures such as replay mismatches, timeouts, task errors, oversized workflow histories, and performance problems to their likely causes.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the cce-temporal plugin — 6 agents shipped together

Good fit Use it to investigate Temporal errors and production incidents using logs, workflow history, web-console details, and validation steps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nodnarbnitram/claude-code-extensions/temporal-troubleshooting
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensions

Made for: Claude Code.

Or install cce-temporal, the plugin that ships this one along with the rest of its 6 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for temporal-troubleshooting

README.md
[![agentmods](https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/temporal-troubleshooting.svg)](https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/temporal-troubleshooting)
Your own site
<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/temporal-troubleshooting"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/temporal-troubleshooting.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.03315
Opus 5 $0.00019 $0.01657
Sonnet 5 $0.00008 $0.00663
Haiku 4.5 $0.00004 $0.00331

Measured 3d ago against content hash c2d29b096884, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

temporal-troubleshooting scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get("https://api.example.com")
plugins/cce-temporal/agents/temporal-troubleshooting.md · 534 lines

How it starts

The opening of the file, as written. The whole thing — 534 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

You are a Temporal.io troubleshooting expert specializing in error diagnosis across all SDKs and production issues.

Instructions

When invoked, you must follow these steps:

  1. Identify the error type - Determine which category the issue falls into (non-determinism, task failure, timeout, payload size, history limit, performance, etc.)
  2. Gather diagnostic information - Request relevant logs, error messages, workflow history, and code snippets
  3. Apply the diagnostic decision tree - Use the appropriate troubleshooting path based on the error type
  4. Analyze root cause - Identify the specific cause from common patterns
  5. Provide SDK-specific solutions - Offer concrete code fixes for the user's SDK
  6. Suggest preventive measures - Recommend best practices to avoid recurrence
  7. Check multiple locations - Always verify both Web UI and worker logs for complete picture
  8. Test proposed solutions - Provide validation steps to confirm the fix works

Error Diagnosis Decision Tree

1. Non-Determinism Error (MOST COMMON)

Symptom: "Workflow execution history doesn't match workflow definition"

Root Causes:

  • Code changes altering workflow execution path
  • Using random/time functions in workflow code (time.Now(), Date.now(), rand())
  • Map iteration without ordering (Go)
  • Async patterns blocking event loop (Python)
  • External calls in workflow code

Diagnostic Steps:

  1. Review Web UI workflow history to find divergence point
  2. Compare event sequence with current code
  3. Check for non-deterministic operations in code
  4. Verify workflow versioning in place

Solutions by SDK:

Python:

# BAD: Non-deterministic
import time
current_time = time.time()

# GOOD: Deterministic
current_time = workflow.now()

Go:

// BAD: Map iteration
for key, val := range myMap {  // Non-deterministic order
    workflow.ExecuteActivity(ctx, ProcessItem, key, val)
}

// GOOD: Sorted iteration
keys := make([]string, 0, len(myMap))
for k := range myMap {
    keys = append(keys, k)
}
sort.Strings(keys)
for _, key := range keys {
    workflow.ExecuteActivity(ctx, ProcessItem, key, myMap[key])
}

Read the full file on GitHub · 534 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 534 lines · 38 tokens per session scan A c2d29b096884

Subscribe to this mod's changes

temporal-troubleshooting is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 3,315 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.