Skip to content

docs: Desktop 1.3.6 release notes and How Agents work guide - #59

Merged
charitra-prem merged 1 commit into
mainfrom
fluso-agent/release-notes-1.3.6
Oct 19, 2026
Merged

charitra-prem merged 1 commit into
mainfrom
fluso-agent/release-notes-1.3.6

Conversation

@fluso-agent

@fluso-agent fluso-agent Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Release notes: Desktop 1.3.6 (2026-10-16). One entry for this week's production promotion. Frontend main 1fc72ba8b..f00768ddd (tag desktop-prod-v1.3.6) and backend master 01d433396..85b7b3f41. Written by hand following the release-notes skill rules, because neither repo has a GitHub release for this promotion that the publish workflow could run from.
  • New page: More about Agents → How Agents work. A concept page for the gap the task-first guides leave: one setup with versions, main conversation vs Manager vs sessions, what the model receives each turn, the three app-access checks, routines as scheduled messages, starting points as copies, and one end-to-end example. Checked against backend dev 67ca97435 and frontend dev f00768ddd.
  • Correction in Routines. schedules.mdx said a routine "waits for your decision" on approvals. On dev, an Ask tool during a routine is refused (interactive_unavailable) unless SERVER_SCHEDULED_RUNS_ASK_FOR_APPROVAL is on, and it defaults to off.

Verified (second pass)

Every bullet was checked against frontend desktop-prod-v1.3.6 and backend master 85b7b3f41, and the Agents page against both repos' dev. All cited changes first shipped in the Oct 16 promotion. Corrections in the latest commit:

  • Pro has no weekly limit (usage_limit_constants.py: Pro has no token quota). Only Free and Plus have an allowance; Plus is 10x Free.
  • Dropped "Pro can start as a trial" (Clerk config, not provable from code) and the links to /resources/pricing, which still lists $19/$99 while the code sells Plus $10 and Pro $30.
  • The approval fix only applied on reconnect. The Calendar fix was skill guidance, not code. The MCP fix sorts IPv4 first. The project fix covers damaged records, not renames.
  • Routines: an overlapping run is held and then sent once, not skipped. A missed time sends one late run. SERVER_SCHEDULED_RUNS_ASK_FOR_APPROVAL does not exist on master and is unset in infra, so the "unless your deployment holds routine approvals" hedge is removed.
  • Inbox bell is in the sidebar footer, not only in Agents.

Still open

  • /resources/pricing is stale (prices, "Four plans", Pro "20x tokens"). Needs a separate fix.
  • Agents work is behind the PostHog agents flag in production, so it is not in the note.
  • About 20 user-facing changes that shipped Aug 14 - Oct 6 were never in any release notes.

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.md source map: agent-routines-page.tsx is now agent-routines.tsx / agent-thread-schedules.tsx.

Checks

  • npm run build passes, and /developers/guides/how-agents-work is exported.
  • cspell finds no issues on the changed files.
  • No em dashes, curly quotes, or banned vocabulary.

Replaces #58 (same tree, re-authored by the bot so it can be approved).

- Add the 2026-10-16 Desktop 1.3.6 release-notes entry, checked against desktop-prod-v1.3.6 and premapp-backend master 85b7b3f41
- Add More about Agents > How Agents work
- Correct routine approval behavior in Routines
@charitra-prem
charitra-prem merged commit 75694ca into main Oct 19, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant