Evidence and archive
write.txt · part 1
Full reference1 text occurrences from packages/opencode/src/tool/write.txt, part 1. Every entry preserves the shipped literal and its saved verdict or selection reason.
File contents and all parts · All files
Shipped text
Writes a file to the local filesystem. Usage: - This tool will overwrite the exi
Source: packages/opencode/src/tool/write.txt, characters 0–623, SHA-256 8b7197b6e3a8ec1d.
Jev judged model-facing (confidence 0.93; role tool). This is a classifier judgment, not proof of delivery.
Readable text: Writes a file to the local filesystem. Usage: - This tool will overwrite the existing file if there is one at the provided path. - If this is an existing file, you MUST use the Read tool first to read the file's contents. This tool will fa…
Writes a file to the local filesystem.
Usage:
- This tool will overwrite the existing file if there is one at the provided path.
- If this is an existing file, you MUST use the Read tool first to read the file's contents. This tool will fail if you did not read the file first.
- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
- Only use emojis if the user explicitly requests it. Avoid writing emojis to files unless asked.