Repository navigation
Vinci Code 0.0.61 tightens its shell file-write checks and no longer marks a run as stopped while a connection retry is pending.
Shell file writes: stricter checks. When echo, printf, tee or a cat heredoc writes a file with the >|, N>|, &> or &>> redirects, Vinci now blocks the command and directs the assistant to its file editor, as it already did for >. Those redirects aimed at /dev/null are still allowed. For interpreter one-liners such as python -c or node -e, and for the sandbox's own project and write-permission checks, Vinci now decides whether a path is inside your project with the operating system's own path resolution, following symbolic links. A path that cannot be resolved this way, such as .. after a folder that does not exist yet, is treated as outside the project. On macOS, the sandbox also protects the links you could replace on the way to protected files, such as credentials and shell startup files. On Linux the destinations of such links stay protected, but the links themselves are not yet protected.
Clearer guidance when a shell write is blocked. Vinci now tells the assistant where it can write: the file editor can create or change files in your project folder, and a file outside it needs your approval. The blocked file is named only for a simple, single-command write to a plain path. The message now limits its scratch-file advice to throwaway diagnostics, so it no longer reads as forbidding saving results the task asked to keep.
Connection retries no longer record a stop. When a connection error, or another error Vinci retries, is followed by a successful retry, the receipt no longer records a stop while the retry is pending, so unattended runs keep going. If retries run out on a connection error, the receipt says how many tries were made and that typing continue resumes. If you send input while a retry is waiting, the retry is cancelled; if the request had ended on that error, the receipt says the retry was cancelled because new input arrived.
Fewer needless retries. A status code such as 503 inside a longer number, glued to letters or in a decimal, such as 15029 tokens, an id like 8fa503c or a dotted fraction of a second like 12:00:00.503, no longer causes a retry on its own.