Coder
The coder family is what makes OpenHuman a viable coding partner instead of a chat window that pretends to know the codebase.
Tools in the family
| Tool | What it does |
|---|---|
file_read | Read a file (with line numbers) |
file_write | Write a new file |
edit_file | Targeted edits - match-and-replace with strict uniqueness checks |
apply_patch | Apply a unified diff |
glob_search | Find files by glob pattern |
grep | Ripgrep-style search across the tree |
list_files | Walk a directory tree |
read_diff | Diff between two files or revisions |
git_operations | Status, diff, log, blame, branch, commit |
run_linter | Run the project's linter |
run_tests | Run the project's test command |
csv_export | Export query results as CSV |
Why these are native
- Edits go through uniqueness checks, so the agent can't accidentally clobber the wrong line
- Reads come back with line numbers the agent can refer to in follow-ups
- Git operations parse output into structured data
- Lint and test runs are wired to the project's actual commands
Workspace scoping
Filesystem tools respect a workspace boundary - the agent can't read or write outside it without explicit permission.
See also
- System & Utilities - Shell, node, npm for the rest of the dev loop
- Agent Coordination - For larger refactors that fan out into subagents