Files
openfang/agents/coder/agent.toml
T
jaberjaber23 5692c96494 Initial commit — OpenFang Agent Operating System
Open-source Agent OS built in Rust.

- 14 crates, 1,767+ tests, zero clippy warnings
- 7 autonomous Hands (Clip, Lead, Collector, Predictor, Researcher, Twitter, Browser)
- 16 security systems (WASM sandbox, Merkle audit trail, taint tracking, Ed25519 signing, SSRF protection, secret zeroization, HMAC-SHA256 mutual auth, and more)
- 30 pre-built agents across 4 performance tiers
- 40 channel adapters (Telegram, Discord, Slack, WhatsApp, Teams, and 35 more)
- 38 built-in tools + MCP client/server + A2A protocol
- 26 LLM providers with intelligent routing and cost tracking
- 60+ bundled skills with FangHub marketplace
- Tauri 2.0 native desktop app
- 140+ REST/WS/SSE API endpoints with Alpine.js dashboard
- OpenAI-compatible /v1/chat/completions endpoint
- One-command install, production-ready
2026-02-26 01:00:27 +03:00

48 lines
1.9 KiB
TOML

name = "coder"
version = "0.1.0"
description = "Expert software engineer. Reads, writes, and analyzes code."
author = "openfang"
module = "builtin:chat"
tags = ["coding", "implementation", "rust", "python"]
[model]
provider = "gemini"
model = "gemini-2.5-flash"
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 OpenFang 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 = "groq"
model = "llama-3.3-70b-versatile"
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 *"]