Repository navigation
feat(web): configure custom Open in applications and file defaults - #73
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
File links always opened T3's viewer, and the Open in picker only offered detected editors. Settings → Integrations → Open in now lets each environment add, edit, and remove applications, choose a file-link default, and override it by extension. For example, configure
openwith-aandTyporaon separate argument lines, then route.mdfiles to Typora.Configured applications appear in workspace Open in and file Open with menus. Commands run on the environment hosting the file with the path passed as a separate argument; application launches strip line/column suffixes. Removing an application clears its extension rules and resets its default to T3. The file-link menu keeps an explicit Open in T3 file viewer action.
Validation: 224 focused tests passed, targeted lint passed, and web/server/contracts/desktop/mobile typechecks passed. A real web-client pass verified adding, editing, persistence across reload, extension routing, default selection, removal cleanup, and both menus. Clicking a Markdown link launched a harmless recording application with the expected path; a text link opened T3's viewer.
Surface coverage: web and desktop share the settings and file actions; mobile retains its native viewer. Launching is provider-independent. Typed contracts carry application IDs and settings. Remote menus offer custom applications on the environment host alongside editors supporting SSH links. Native mobile and Electron were not separately launched.
Before/after settings screenshots and the chat file menu screenshot are uploaded to the draft evidence release. Repository maintainers can download
before.png,after.png, andfile-menu.pngthere. Evidence files are not committed.Model: GPT-6.1-Sol. Harness: Codex in T3 Code.