-
Notifications
You must be signed in to change notification settings - Fork 0
Agent Instructions
Jarvis Line speaks concise status lines that the agent deliberately emits. The instruction block must therefore be present in the Markdown instruction file the active agent actually reads.
Jarvis Line prints the block for review. It does not edit your instruction file by default because only you know the right agent and project/global scope.
| Scope | Use it when | Common location |
|---|---|---|
| Project | Jarvis Line should apply only in one repository or workspace |
./AGENTS.md, ./CLAUDE.md, or ./GEMINI.md
|
| Global/user | The same behavior should apply across many projects | Your agent's global instruction file |
Paste the generated ## Jarvis Line block into the file you chose. If the
block is absent from the file your agent reads, the runtime can be installed
and healthy while no Jarvis line: ... is produced.
Codex or generic AGENTS.md:
jarvis-line instructions print agents --language "English"Claude:
jarvis-line instructions print claude --language "English"Gemini:
jarvis-line instructions print gemini --language "English"Shorter instruction variant:
jarvis-line instructions print agents --language "English" --style minimalThe command prints Markdown to standard output. It does not choose a path or write a file.
Use the full language name you want spoken:
jarvis-line instructions print agents --language "English"
jarvis-line instructions print agents --language "Turkish"
jarvis-line instructions print agents --language "German"
jarvis-line instructions print agents --language "Japanese"
jarvis-line instructions print agents --language "Brazilian Portuguese"There is no automatic "user language" mode. The language in this command tells
the agent what language to use for Jarvis line: text. Your TTS voice or model
must support the same language.
Examples:
- English instruction + English Kokoro voice: good default
- Turkish instruction + Turkish macOS Read & Speak voice: valid
- Turkish instruction + English Kokoro defaults: likely robotic or mispronounced
See TTS and Voices before choosing a non-English backend.
- exactly one
Jarvis line: ...in each final response - one short line in meaningful commentary/progress updates
- one natural sentence rather than a transcript
- status, completion, or next-action content only
- no secrets, raw logs, code, private data, or long file contents
- normal user-facing text can remain in a different language
Example:
Jarvis line: The implementation is complete and verified.
The goal is to summarize what the agent is doing now and when it finishes, not to read the full conversation aloud.
After pasting the block:
jarvis-line instructions doctor agentsUse claude or gemini instead of agents for the corresponding generated
target.
instructions install exists for disposable files and advanced workflows that
explicitly want automatic editing:
jarvis-line instructions install agents --language "English" --replaceFor normal project and global instruction files, manual review and paste remain the recommended path.
| Agent | Instruction generation | Bundled native hook/session adapter |
|---|---|---|
| Codex | Yes | Yes |
| Claude | Yes | No; use explicit event protocol for native events |
| Gemini | Yes | No; use explicit event protocol for native events |
| Other agents | Generic block | Supply a protocol adapter |
See Platform and Agent Support for the current validation level.
Repository · Releases · Issues · Discussions