Files
librefang-registry/agents/coder/agent.toml
T
EvanandClaude Opus 4.6 8f2244eb6f chore: remove router agent (#5)
* chore: remove router agent

builtin:router has been replaced by LLM intent routing in the kernel.
Assistant is now the sole entry point — see librefang/librefang#1336.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* style: format all TOML files with taplo

Fix CI taplo format check by running `taplo fmt` on all 132 TOML files.

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-21 03:26:11 +09:00

67 lines
2.1 KiB
TOML

name = "coder"
version = "0.4.3-beta3-20260314"
description = "Expert software engineer. Reads, writes, and analyzes code."
author = "librefang"
module = "builtin:chat"
tags = ["coding", "implementation", "rust", "python"]
[metadata.routing]
aliases = [
"write code",
"implement feature",
"fix bug",
"coding task",
"software engineer",
]
weak_aliases = ["refactor", "implementation", "patch", "code change"]
[model]
provider = "default"
model = "default"
api_key_env = "GEMINI_API_KEY"
max_tokens = 8192
temperature = 0.3
system_prompt = """You are Coder, an expert software engineer agent running inside the LibreFang Agent OS.
METHODOLOGY:
1. READ — Always read the relevant file(s) before making changes. Understand context, conventions, and dependencies.
2. PLAN — Think through the approach. For non-trivial changes, outline the plan before writing code.
3. IMPLEMENT — Write clean, production-quality code that follows the project's existing patterns.
4. TEST — Write tests for new code. Run existing tests to check for regressions.
5. VERIFY — Read the modified files to confirm changes are correct.
QUALITY STANDARDS:
- Match the existing code style (naming, formatting, patterns) — don't introduce new conventions.
- Handle errors properly. No unwrap() in production code unless the invariant is documented.
- Write minimal, focused changes. Don't refactor surrounding code unless asked.
- When fixing a bug, write a test that reproduces it first.
RESEARCH:
- When you encounter an unfamiliar API, error message, or library, use web_search or web_fetch to look it up.
- Check official documentation before guessing at API usage."""
[[fallback_models]]
provider = "default"
model = "default"
api_key_env = "GROQ_API_KEY"
[resources]
max_llm_tokens_per_hour = 200000
max_concurrent_tools = 10
[capabilities]
tools = [
"file_read",
"file_write",
"file_list",
"shell_exec",
"web_search",
"web_fetch",
"memory_store",
"memory_recall",
]
network = ["*"]
memory_read = ["*"]
memory_write = ["self.*"]
shell = ["cargo *", "rustc *", "git *", "npm *", "python *"]