Skip to content

v0.176.0

Choose a tag to compare

@github-actions github-actions released this 24 Sep 09:34
· 317 commits to main since this release
43c6199

What's new

  • Open in Zed / VS Code / Cursor links on file-tool results, including the desktop app (#3596). Paths in read_file, search_files, find_files, write_file and edit_file results are now links that open the file in your editor. A search_files hit opens at its line, and a read_file opens at the line it read from. Pick the editor under Settings ▸ This console ▸ Chat ▸ Open files in: Zed (the default), VS Code, Cursor, or Off for plain text. The setting is saved per browser, because the editor belongs to your machine, not the agent.
    • Links only work when the console and the agent share a filesystem, as in the desktop app or a local server. A remote agent's paths won't exist on your machine.
    • Links are built from a new read-only GET /api/fs/roots, which uses the same project fence as the filesystem tools. A link can't point outside a managed project.
  • open_in_editor agent tool (filesystem.editor_command) (#3597). Set filesystem.editor_command to your editor's command line (zed, code -g, cursor -g) and an agent on your own machine can open a file for you, jumping to a line if one is given ("open the router for me"). It resolves paths through the same fence as every filesystem tool, works in read-only projects, launches the editor without waiting on it, and opens files only, not directories. Leave the setting empty (the default) and the tool is not offered. Don't set it on a headless or remote agent.
    • Windows: point editor_command at the editor's real .exe, quoted if the path has spaces, e.g. "C:\Users\<you>\AppData\Local\Programs\Microsoft VS Code\Code.exe" -g. A .cmd/.bat launcher is refused. VS Code's code command is code.cmd, and Windows runs batch launchers through cmd.exe, which would interpret characters in file names.

Desktop

  • The desktop app passes editor links to your OS under a strict allowlist. Only zed://file/…, vscode://file/… and cursor://file/… links pass, and only when they point at an existing file on a local disk. Other link schemes, directories, .code-workspace files, paths containing .., and Windows network (UNC) paths are refused.

What's Changed

  • feat(fs): config-gated open_in_editor tool (filesystem.editor_command) by @mabry1985 in #3597
  • feat(console): open fs tool paths in Zed / VS Code / Cursor by @mabry1985 in #3596

Full Changelog: v0.175.0...v0.176.0