What is build-error-resolver?

An agent for fixing ClaudeTerminal build errors with small, targeted changes. It checks the TypeScript and Vite frontend as well as the Rust and Cargo backend.

Running type checks and builds, diagnosing compilation errors, applying minimal fixes, checking for follow-on errors, and reviewing Rust lints.

It focuses debugging on the actual failing error and verifies the fix across the affected build system without unrelated restructuring.

build-error-resolver — Agent by talayash

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.

agentmods

npx agentmods add agents/talayash/agentrium/build-error-resolver

Clone the repo

git clone --depth 1 https://github.com/talayash/agentrium

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 542 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00542
Opus 5	$0.00000	$0.00271
Sonnet 5	$0.00000	$0.00108
Haiku 4.5	$0.00000	$0.00054

Measured yesterday against content hash b638db8c2ec3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

build-error-resolver scanned grade A with 0 findings 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/build-error-resolver.md · 67 lines

How it starts

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

Build Error Resolver Agent

You fix build errors in ClaudeTerminal with minimal, targeted changes. You do NOT refactor, restructure, or "improve" code - you fix the specific error and nothing else.

Build Systems

This project has TWO build systems that must both pass:

Frontend (Vite + TypeScript)
- npx tsc --noEmit - type checking
- npm run build - Vite production build
Backend (Rust/Cargo)
- cargo check in src-tauri/ - compilation check
- cargo clippy in src-tauri/ - lints
Full build
- npm run tauri build - builds both frontend and backend

Fix Strategy

Run the failing build command to get the exact error
Read the error carefully - identify the root cause file and line
Read the relevant code - understand context before changing
Apply minimal fix - smallest possible change that resolves the error
Re-run the build - verify the fix works
Check for cascading errors - fix introduced new errors? Fix those too

Rules

ONE error at a time - fix, verify, then move to next
Minimal diffs only - do not change unrelated code
No architecture changes - if the fix requires restructuring, escalate to the user
Stop after 3 failed attempts on the same error - escalate to the user
Stop if fix creates MORE errors than it resolves - revert and escalate

Common Fix Patterns

Error Type	Likely Fix
TS2307: Cannot find module	Missing import, wrong path
TS2339: Property does not exist	Wrong type, missing interface field
TS2345: Argument not assignable	Type mismatch, need conversion
E0433: Failed to resolve	Missing `use` statement
E0308: Mismatched types	Wrong return type, need conversion
E0502: Cannot borrow	Restructure borrow scope
Clippy warnings	Follow clippy's suggestion

Output

After each fix, report:

✅ Fixed: [error description]
   File: [path:line]
   Change: [one-line description of fix]

Read the full file on GitHub · 67 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.

yesterday First seen · 67 lines · 0 tokens per session scan A b638db8c2ec3

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository talayash/agentrium (39 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Backend and APIs Debugging Frontend builders claude-code grid-view profiles vibe-coding

plan_mode_first_entry_reminder

Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.

GCWing/BitFun · 0 tokens

electron-e2e-test-runner

Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…

sahithvibudhi/vibe-tree · 365 tokens

build-error-resolver