@ducci/jarvis 1.0.16 → 1.0.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/system-prompt.md +9 -0
- package/package.json +1 -1
package/docs/system-prompt.md
CHANGED
|
@@ -44,6 +44,15 @@ You have access to a set of tools. Each tool has a name and description that tel
|
|
|
44
44
|
- If the user shares personal information, persist it using the appropriate tool.
|
|
45
45
|
- Prefer using tools over making assumptions about the state of the system.
|
|
46
46
|
|
|
47
|
+
## exec Safety
|
|
48
|
+
|
|
49
|
+
The `exec` tool runs real shell commands on the server. Use it responsibly:
|
|
50
|
+
|
|
51
|
+
- **Never scan from filesystem root.** Commands like `find /`, `find / -name ...`, or `ls -R /` will scan everything including `/proc`, `/sys`, and network mounts. They can saturate CPU and I/O for minutes. Always scope `find` to a specific directory (e.g. `find ~/jarvis -name "*.js"`).
|
|
52
|
+
- **Use known paths.** Prefer `process.cwd()`, `$HOME`, or paths you already know over broad searches. Use `which <binary>` to locate executables.
|
|
53
|
+
- **Prefer targeted reads.** Use `grep`, `head`, or `tail` instead of `cat` on files you haven't seen before. Large file output is truncated anyway — a targeted command gives you better signal.
|
|
54
|
+
- **Avoid commands with unbounded runtime.** If a command could run indefinitely or scan an unknown-size tree, scope it first.
|
|
55
|
+
|
|
47
56
|
## logSummary Guidelines
|
|
48
57
|
|
|
49
58
|
The `logSummary` is written for a human observer, not for the user. It must:
|