Uh oh!
There was an error while loading. Please reload this page.
docs: name the model per path, and drop network egress - #42
Merged
Conversation
added 3 commits
August 19, 2026 20:31
Kimi K3 is the default for standard chats. Confidential Mode ran its own model on the encrypted path in this release, GLM 5.2. The entry said only "Kimi K3 becomes the default model", which reads as if it covers confidential users too.
Confidential requests all run through DeepSeek V4 Flash now, so the entry names it rather than the model that path started on.
Egress is off and the frontend surfaces for it are gone (fluso-frontend #417). Approvals are connector and MCP tool approvals only. - approvals: two modes instead of three, no network approval cards, no network rule editor, no hostname troubleshooting. The mode video, the settings video and the settings screenshot all showed the network UI, so they come out until fresh captures exist. - chat: the approval-mode section no longer mentions network access. - release notes 1.5.0: the highlight is about tools, the network-card bullet is gone, and so is the permissions walkthrough, which #417 removed with the rest of the egress announcement.
charitra-prem
approved these changes
Aug 19, 2026
charitra-prem
approved these changes
Aug 19, 2026
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Two corrections to the live docs.
1. Which model each path runs. The v1.5.0 entry said "Kimi K3 becomes the default model", which reads as if it covers confidential users too. Kimi K3 is the default in standard chats; every confidential request goes through DeepSeek V4 Flash.
2. Network egress is gone. Egress is off and the frontend surfaces for it were removed in fluso-frontend#417, so the docs still described a feature that no longer exists. Approvals are connector and MCP tool approvals only now.
features/approvals.mdx- two modes instead of three (ask-criticalwas retired and migrated toask-everything), no network approval cards, no network rule editor, no hostname troubleshooting.features/chat.mdx- the approval-mode section no longer mentions network access.release-notes.mdx(2026-08-14 entry) - the highlight is about tools, the network-card bullet is gone, and the permissions walkthrough bullet goes too since #417 removed that announcement.Needs follow-up: the two videos and the settings screenshot on the approvals page all showed the three-mode selector and the network access editor, so they are removed here rather than left contradicting the text. They need fresh captures of the current UI.
🤖 Generated with Claude Code