Evan
7881d327a5
* refactor: migrate icon fields from emoji to lucide:<name> tokens
Every TOML manifest's `icon = "<emoji>"` line is replaced with
`icon = "lucide:<kebab-name>"` — a reference to a lucide-react icon,
which the librefang.ai site and dashboard render as crisp SVG. Reasons
for the switch:
- Emoji render very differently across OS/browser/font stacks; the
registry catalog looked inconsistent from one row to the next.
- Five manifests (clip / creator / linkedin / reddit / twitter) had
their icons stored as literal Python-style escape strings
("\\U0001F3AC") because the TOML parser upstream never decoded
them. Switching away from emoji drops that class of bug entirely.
- As a drive-by, also decode the \\uXXXX accent escapes in the
[i18n.fr] block of hands/creator/HAND.toml so "Créateur" shows
up correctly.
87 files touched. example manifests left untouched (still "TODO").
* fix: backfill i18n name + drop the single-member email category
- Every existing [i18n.<lang>] block now has a `name` field. 60 files
previously translated description but kept the English name
implicitly — which rendered as "some English some Chinese" in the
registry UI. Fill in the missing name from the English brand (or a
known localized equivalent: DingTalk→钉钉, Feishu→飞书, Email→
电子邮件 / メール / E-Mail / Correo / Courriel, and a handful of
hands that have Chinese product names like 视频剪辑 Hand).
- channels/email.toml was the only item under category="email";
reclassify it as "messaging" so the sub-category filter chip list
on the category page isn't littered with singletons.
* feat(i18n): localize 76 agents/integrations/plugins into 7 languages
Adds full [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks with name + description to every manifest
that previously shipped English-only.
Coverage:
- 32 agents (academic-researcher, analyst, architect, assistant,
code-reviewer, coder, customer-support, data-scientist, debugger,
devops-lead, doc-writer, email-assistant, health-tracker,
hello-world, home-automation, legal-assistant, meeting-assistant,
ops, orchestrator, personal-finance, planner, recipe-assistant,
recruiter, researcher, sales-assistant, security-auditor,
social-media, test-engineer, translator, travel-planner, tutor,
writer)
- 33 integrations (AWS, Azure, Bitbucket, Brave Search, Discord,
Dropbox, Elasticsearch, Exa Search, Fetch, Filesystem, GCP, Git,
GitHub, GitLab, Gmail, Google Calendar, Google Drive, Google Maps,
Jira, Linear, Memory, MongoDB, Notion, PostgreSQL, Puppeteer, Redis,
Sentry, Sequential Thinking, Slack, SQLite, Teams, Time, Todoist) —
brand names kept as-is across all locales, only descriptions
translated.
- 11 plugins (auto-summarizer, context-decay, conversation-logger,
episodic-memory, guardrails, keyword-memory, mempalace-indexer,
sentiment-tracker, todo-tracker, topic-memory, user-profile)
The descriptions are one-line summaries — hand-translated rather than
machine-generated, so technical terms (MCP, PR, CI/CD, etc.) stay
consistent across locales.
* feat(i18n): close remaining per-lang gaps for channels, workflows, devteam
Third pass on i18n coverage. Every non-example manifest now carries a
full set of [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks.
- 44 channel adapters: added French descriptions (zh/zh-TW/ja/ko/de/es
were already present). Brand names kept as-is in all locales so users
recognize Discord / Slack / LINE / etc. consistently.
- 22 workflows: filled zh-TW / ja / ko / de / es / fr blocks. Each
translation mirrors the existing zh one in structure and tone so the
catalog reads consistently across locales.
- hands/devteam/HAND.toml: added the four langs that were missing
(zh-TW, de, es, fr).
Only the 6 templates under examples/ are left without i18n blocks on
purpose — they still contain "TODO:" placeholders.
101 lines
3.1 KiB
TOML
101 lines
3.1 KiB
TOML
name = "debugger"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Expert debugger. Traces bugs, analyzes stack traces, performs root cause analysis."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"debug this",
|
|
"root cause analysis",
|
|
"investigate bug",
|
|
"trace the bug",
|
|
"analyze stack trace",
|
|
]
|
|
weak_aliases = ["debug", "bug", "stack trace", "reproduce issue"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
max_tokens = 4096
|
|
temperature = 0.2
|
|
system_prompt = """You are Debugger, an expert bug hunter running inside the LibreFang Agent OS.
|
|
|
|
DEBUGGING METHODOLOGY:
|
|
1. REPRODUCE — Understand the exact failure. Get the error message, stack trace, or unexpected behavior.
|
|
2. ISOLATE — Read the relevant source files. Use git log/diff to check recent changes. Narrow the search space.
|
|
3. IDENTIFY — Find the root cause, not just symptoms. Trace data flow. Check boundary conditions.
|
|
4. FIX — Propose the minimal correct fix. Don't refactor — just fix the bug.
|
|
5. VERIFY — Write or suggest a test that catches this bug. Run existing tests.
|
|
|
|
COMMON PATTERNS TO CHECK:
|
|
- Off-by-one errors, null/None handling, race conditions
|
|
- Resource leaks (file handles, connections, memory)
|
|
- Error handling paths (what happens on failure?)
|
|
- Type mismatches, silent truncation, encoding issues
|
|
- Concurrency bugs: shared mutable state, lock ordering, TOCTOU
|
|
|
|
RESEARCH:
|
|
- When you see an unfamiliar error message, use web_search to find known causes and fixes.
|
|
- Check issue trackers and Stack Overflow for similar reports.
|
|
|
|
OUTPUT FORMAT:
|
|
- Bug Report: What's happening and how to reproduce it
|
|
- Root Cause: Why it's happening (with code references)
|
|
- Fix: The specific change needed
|
|
- Prevention: Test or pattern to prevent recurrence"""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GROQ_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 150000
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"shell_exec",
|
|
"web_search",
|
|
"web_fetch",
|
|
"memory_store",
|
|
"memory_recall",
|
|
]
|
|
network = ["*"]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
shell = ["cargo *", "git log *", "git diff *", "git show *", "python *"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "调试专家"
|
|
description = "调试专家：追踪 Bug、分析堆栈、定位根因。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "除錯專家"
|
|
description = "除錯專家：追蹤 Bug、分析堆疊、定位根因。"
|
|
|
|
[i18n.ja]
|
|
name = "デバッガー"
|
|
description = "バグの追跡、スタックトレース解析、根本原因分析を行うエキスパート。"
|
|
|
|
[i18n.ko]
|
|
name = "디버거"
|
|
description = "버그 추적, 스택 트레이스 분석, 근본 원인 분석을 수행하는 전문가."
|
|
|
|
[i18n.de]
|
|
name = "Debugger"
|
|
description = "Experte für Bug-Tracing, Stack-Trace-Analyse und Root-Cause-Analysis."
|
|
|
|
[i18n.es]
|
|
name = "Depurador"
|
|
description = "Experto en rastreo de bugs, análisis de stack traces y análisis de causa raíz."
|
|
|
|
[i18n.fr]
|
|
name = "Débogueur"
|
|
description = "Expert en traçage de bugs, analyse de piles d'appels et recherche de causes racines."
|