# What to check after Factory Droid 1.16 locks session sync

Factory Droid 1.16 removes the session-content sync opt-out on non-Enterprise plans. Check what gets stored and which workflows rely on sync before updating your team's runbook.

By Paras Madan | 2026-11-21


Installing a coding agent on your laptop does not tell you where its conversation history is stored. That distinction matters after [Factory Droid 1.16.0](https://docs.factory.com/changelog/release-notes), released November 20 for the CLI and desktop app. Factory says plans outside Enterprise can no longer turn off Session Contents Sync, and the control now appears locked.

If your team chose Droid on the assumption that transcripts could stay on the machine, revisit that decision before using the tool on a new repository. Start by checking the plan and the effective setting, not just the old configuration file.

## Read the release note before the settings reference

The [CLI settings reference](https://docs.factory.com/droid-cli/settings#cloud-session-sync) describes `cloudSessionSync` and what its enabled and disabled states mean. It also says an organization choice takes precedence over an individual preference. Neither description means both choices remain available to every account after the update.

Write down the Droid version, the active organization and the plan when you check the setting. A developer who works in two organizations should not assume that what they saw in one applies to the other. If a non-Enterprise account depended on the local-only option, mark that workflow for review rather than leaving developers to discover the lock mid-task. A setting copied forward from an earlier runbook is not proof of effective behavior.

## Separate the transcript from the session record

With sync enabled, the [Factory App settings guide](https://docs.factory.com/factory-app/settings#cloud-session-sync) says sessions are mirrored to the Factory App for later access. That is different from saying source files on a developer's disk are all uploaded. The question for a team is what happens to content that enters the coding session.

For Enterprise organizations, [Factory's managed-settings documentation](https://docs.factory.com/enterprise/hierarchical-settings-and-org-control#session-contents-sync) distinguishes session contents from metadata. Turning off contents sync keeps the transcript on the originating machine, but Factory still stores metadata such as session IDs, timestamps and tags. Titles and workstream shared folders have separate controls when content sync is off.

Record those categories separately in your runbook. A policy that permits session IDs but not conversation content is not the same as one that requires no remote records at all. Avoid the phrase “everything stays local” unless you can say precisely which data and systems you mean.

## Check the workflows that rely on sync

On Enterprise, treat a change as an organization decision, not a developer preference. The admin guide says that with content sync off, accessing the conversation from another device depends on the originating machine being online. Sharing with `/share` is unavailable, and some remote workstream configurations require sync.

Pick two normal workflows and walk through them with your admin. For example, can someone open a saved session from another device when the originating laptop is offline? Can the team review a handoff without a shared session? If not, move the handoff to the approved place your team already uses for project records, such as the pull request or issue, rather than relying on a console setting nobody checked.

## Use a harmless pilot before changing your runbook

Open a test project with generated files and start a session containing a unique, non-sensitive marker. Record what you can see from the original machine and from the Factory App. An Enterprise admin evaluating sync-off can also check what happens when the originating machine is unavailable, using only that disposable session.

This can check the behavior your team sees, but it is not proof that no data was stored elsewhere or that older history was deleted. Use the provider's documented policy and your own requirements for those decisions. The release note does not explain what happens to all pre-upgrade transcripts, so do not infer retroactive upload or deletion from the locked switch.

## Decide who can use the updated workflow

If contents sync is required by your plan but not allowed for the planned work, stop using that account for the workflow until the team has approved a suitable configuration or tool. If sync is allowed, document which projects are in scope, where handoffs should go and who owns periodic review. Those decisions are more useful than a screenshot of the switch.

## Make product changes easier to act on

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help AI and developer tool teams turn releases and rollout decisions into technical writing and product stories developers can use.

[Book a 30-minute call](https://cal.com/paras-madan/30min).
