Privacy-first terminal coding agent with MCP support, sub-agents, workflows, and verifiable TEE inference. Supports 20+ LLM providers with safe-by-default permissions.
Privateer Agent exposes 11 tools, but only 2 have visible explicit definitions in the provided source (create_routine, read_routine_result in extensions/privateer-tools.ts). The remaining 9 tools (send_file_to_client, save_attachment, save_cargo, save_to_library, video_compose, read, grep, find, ls) are referenced but their actual schema definitions, parameter types, and descriptions are not visible in the provided code. The two visible tools (routine, routineResult) lack detailed parameter descriptions and output schemas in the excerpt. No tool shows input validation, error recovery guidance, or structured output documentation. Descriptions are present but generic (e.g., 'Schedule unattended tasks'). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are visible. The codebase references Pi toolkit builtins and MCP adapters, but the actual tool registration code with full schemas is not provided.
Schedule unattended tasks that the harbor runs
Find files (builtin Pi tool)
Search file contents (builtin Pi tool)
List directory contents (builtin Pi tool)
Read file contents (builtin Pi tool)
Read a routine's standing instruction and latest output so a conversation can act on what a routine found
Save an attachment to the attachment store
Save cargo/artifacts to the connected app
No input schemas visible for any tool.
Descriptions are generic and under 50 characters for most tools. 'Schedule unattended tasks' and 'Read a routine's standing instruction' lack context on WHEN to use, WHAT happens, and WHAT is returned.
No parameter descriptions visible. Even for the two explicitly defined tools (create_routine, read_routine_result), parameter names and types are not shown in the provided source.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | 2026-07-28+ | v2 |
Save content to the user's library with encryption
Send a file to the connected client via relay bridge
Compose videos locally using ffmpeg
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) visible. Tools like save_attachment, save_cargo, save_to_library, and video_compose are marked WRITE risk but lack destructiveHint annotation to signal to LLMs that these are state-modifying operations.
No error handling or recovery guidance visible. Tools lack descriptions of failure modes, retryability, or actionable error messages. Per pattern:recovery-guide, errors must tell the LLM what to do next.