v4.100.245

Commands whose end VS Code never reports

VS Code has open faults where a command sent to the terminal finishes but the
extension is never told: for some multi-line commands and ( ... ) subshells
the end signal is lost, and for some no output is delivered at all
(microsoft/vscode#250764, #316556, #324392). The command sat "running" until
the five-minute limit while the terminal was back at its prompt.

Three cases now end on their own:

• The end marker was read but the stream stayed open: the command finishes two
  seconds later, with its exit code.
• Output arrived, nothing reported the end, and the shell's own prompt has been
  the last thing printed for ten seconds: the command is treated as finished,
  and the result says the exit code is unknown. This applies to Windows prompts
  (PS C:\path>, C:\path>).
• The command started and nothing else arrived: the result says the output was
  not delivered, gives the terminal's visible contents, and suggests sending the
  command on one line or from a file.

A command the shell never started is still reported as such; the two are told
apart by whether VS Code saw the command start.

Code search by meaning

The model can now find code by describing it. In a folder you opt in,
search_codebase gains a semantic mode: the query is a question in plain
words ("where is a user's password checked") and the answer is the passages
that best match, each with its file and lines. It is for when the model does
not know what a thing is called; regex search and ask_lsp are still what it
uses when it does.

• Off by default, on per folder: Settings > Library > Index the code of
  this folder. Building the index sends every source file of the folder to the
  embedding model set in the API configuration.
• Files .gitignore leaves out are left out, and so are binaries, lockfiles,
  generated files and anything over 256 KB.
• The index is brought up to date when a task starts and with Update now;
  only changed files are read and embedded again.
• In a folder that is not indexed the tool is unchanged.
• Not yet offered to agents started by the lead, and not in the CLI.