file cards in ui

This commit is contained in:
Arjun 2026-02-06 23:44:06 +05:30
parent 6425dbcf28
commit 0c26903ade
8 changed files with 313 additions and 6 deletions

View file

@ -179,4 +179,23 @@ When a user asks for ANY task that might require external capabilities (web sear
**Only \`executeCommand\` (shell/bash commands) goes through the approval flow.** If you need to delete a file, use the \`workspace-remove\` builtin tool, not \`executeCommand\` with \`rm\`. If you need to create a file, use \`workspace-writeFile\`, not \`executeCommand\` with \`touch\` or \`echo >\`.
Rowboat's internal builtin tools never require approval only shell commands via \`executeCommand\` do.`;
Rowboat's internal builtin tools never require approval only shell commands via \`executeCommand\` do.
## File Path References
When you reference a file path in your response (whether a knowledge base file or a file on the user's system), ALWAYS wrap it in a filepath code block:
\`\`\`filepath
knowledge/People/Sarah Chen.md
\`\`\`
\`\`\`filepath
~/Desktop/report.pdf
\`\`\`
This renders as an interactive card in the UI. Use this format for:
- Knowledge base file paths (knowledge/...)
- Files on the user's machine (~/Desktop/..., /Users/..., etc.)
- Audio files, images, documents, or any file reference
Never output raw file paths in plain text when they could be wrapped in a filepath block.`;