Tools
Jarvis gives managed coding sessions a small set of worker-facing tools so they can report status and ask for help without dumping full raw tool output into the main chat.
Why these tools exist
Section titled “Why these tools exist”The goal is operational clarity:
- workers can report progress,
- blocked work can surface quickly,
- human decisions can be requested explicitly,
- extra context can be requested without breaking the session flow.
This keeps the main conversation readable while still giving the user control.
Core worker tools
Section titled “Core worker tools”report_progress
Section titled “report_progress”Use this when a worker has meaningful forward movement to report.
Typical uses:
- a task phase finished,
- a test passed,
- a document draft is ready for review,
- the worker wants the main session to see a compact status update.
notify_blocked
Section titled “notify_blocked”Use this when a worker cannot continue without an external decision, missing resource, or unresolved failure.
Typical uses:
- credentials are missing,
- a command depends on unavailable infrastructure,
- the worker hit a hard product ambiguity,
- a repeated failure needs escalation instead of more retries.
ask_human
Section titled “ask_human”Use this when the worker needs a decision from the user rather than only reporting state.
Typical uses:
- choose between two implementation options,
- approve a risky step,
- provide a missing value,
- confirm a product decision.
request_context
Section titled “request_context”Use this when the worker needs more context from the main Jarvis session to continue safely.
Typical uses:
- another session has the missing information,
- the worker needs related history,
- the current prompt lacks required scope or intent.
Optional knowledge-base tool
Section titled “Optional knowledge-base tool”search_kb
Section titled “search_kb”search_kb is an optional worker tool for personal knowledge-base lookup.
Public behavior should be documented this way:
- it is optional,
- it is user-specific,
- it must not assume a fixed local path,
- it should degrade gracefully when not configured.
If the knowledge base is unavailable, the tool should return an unavailable status rather than crashing the worker or leaking private path details.
Tool behavior and privacy
Section titled “Tool behavior and privacy”These tools are intentionally compact. They help Jarvis preserve a cleaner main chat context than a full raw tool transcript would.
That matters for:
- readability,
- debugging,
- privacy,
- long-running orchestration.
When describing worker tools publicly, focus on behavior and boundaries. Do not document private prompt content, private knowledge-base entries, or user-specific filesystem details.