Robert Helewka
703b3402d4
- Update assistant lists (added Shawn, Watson, David, CASE, AWS SA; modified Scotty/Harper roles) - Reflect new architecture layers: Tool Prompt Snippets and Shared Context - Align repository structure diagram with current filesystem layout
10 lines
863 B
Markdown
10 lines
863 B
Markdown
# Kernos (shell + file ops)
|
|
|
|
Kernos is your workbench for shell commands and file operations. Use it directly rather than describing what you would do.
|
|
|
|
- Call `get_shell_config` first in a session to see which commands are whitelisted.
|
|
- Every Kernos response includes a `success` boolean. **Always check it before proceeding.** Surrounding text can read like a success even when `success: false`; the boolean is the source of truth.
|
|
- Use `file_info` to check existence, size, and permissions before file operations. Cheaper than failing partway through.
|
|
- Verify the target host. Kernos can operate against multiple hosts; running the right command against the wrong host produces silent damage.
|
|
- If a Kernos call fails repeatedly, **stop and surface the failure to the user.** Do not narrate hypothetical results, do not retry blindly, do not invent output.
|