Repository navigation
docs: Desktop 1.3.6 release notes and How Agents work guide - #58
Closed
charitra-prem wants to merge 2 commits into
Closed
charitra-prem wants to merge 2 commits into
charitra-prem wants to merge 2 commits into
Conversation
- Release notes for the 2026-10-16 production promotion (Desktop 1.3.6 plus the backend cycle behind it). - New concept page under More about Agents: setup versions, what the model sees each turn, the three app-access checks, routines as scheduled messages, and a worked example. - Correct the routines page: an Ask tool is refused during a routine unless the deployment holds routine approvals.
Checked against desktop-prod-v1.3.6 and premapp-backend master 85b7b3f41: Pro has no weekly limit, drop the unverified Pro trial and stale pricing links, narrow the approval, Calendar, MCP and project fixes to what shipped, and fix how routines handle overlapping and missed runs.
charitra-prem
marked this pull request as ready for review
October 19, 2026 17:35
Contributor
Author
|
Replaced by #59 (same changes, bot-authored so it could be approved). Merged and live on docs.fluso.ai. |
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.
Summary
main1fc72ba8b..f00768ddd(tagdesktop-prod-v1.3.6) and backendmaster01d433396..85b7b3f41. Written by hand following therelease-notesskill rules, because neither repo has a GitHub release for this promotion that the publish workflow could run from.dev67ca97435and frontenddevf00768ddd.schedules.mdxsaid a routine "waits for your decision" on approvals. Ondev, an Ask tool during a routine is refused (interactive_unavailable) unlessSERVER_SCHEDULED_RUNS_ASK_FOR_APPROVALis on, and it defaults to off.Verified (second pass)
Every bullet was checked against frontend
desktop-prod-v1.3.6and backendmaster85b7b3f41, and the Agents page against both repos'dev. All cited changes first shipped in the Oct 16 promotion. Corrections in the latest commit:usage_limit_constants.py: Pro has no token quota). Only Free and Plus have an allowance; Plus is 10x Free./resources/pricing, which still lists $19/$99 while the code sells Plus $10 and Pro $30.SERVER_SCHEDULED_RUNS_ASK_FOR_APPROVALdoes not exist onmasterand is unset in infra, so the "unless your deployment holds routine approvals" hedge is removed.Still open
/resources/pricingis stale (prices, "Four plans", Pro "20x tokens"). Needs a separate fix.agentsflag in production, so it is not in the note.Left out of the release notes
Daemon
dev-channel pre-releases v0.0.9–v0.0.12, Fluso Local workspace settings (disabled in production), background jobs (off by default), traces/metrics/logging (opt-in), ARM64 release publishing, admin refresh deadlock fix, reconcile diagnostics, CI and test changes. Mobile 1.0.8 went to TestFlight only.Follow-ups found while checking Agent docs (not in this PR)
agent-builder.mdx: unfinished setups appear as sidebar rows ("Setting up · continue with the manager"). Continue setup is a retry on the import page.guides/settings.mdx: the connector labels are Allow / Read only / Deny, and some skills stay on when you narrow the list.README.mdsource map:agent-routines-page.tsxis nowagent-routines.tsx/agent-thread-schedules.tsx.Checks
npm run buildpasses, and/developers/guides/how-agents-workis exported.cspellfinds no issues on the changed files.