DevAgentRadar → Factory Droid

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

Context

Assistant: Factory Droid Proposal: Keep Droid Computer model settings across launches and hide legacy models Summary: Factory Droid v0.231.0 / Desktop v0.188.0 persists Computer model and settings at launch, groups older models behind a legacy toggle, pages full terminal history with Alt/Option+arrows, auto-refreshes stale templates, and restarts crashed MCP servers on the next call. Primary source: https://docs.factory.ai/changelog/release-notes.md

Why it matters

This release changes how you pick models and resume work. The picker now groups older models under a legacy toggle and marks them clearly, so leaving that toggle off keeps current models in front. Launching on a Droid Computer now keeps the model and settings you chose, while those controls stay disabled while a Computer provisions from a template—set them once instead of re-selecting after every launch. Local sessions no longer wait for the template list, and Droid Computer templates refresh on their own when they fall out of date, so you should start immediately and stop refreshing templates by hand. In the terminal, Alt/Option plus the arrow keys pages a session’s full saved history, which is the new way to review long transcripts. Side chat now accepts multi-line messages and no longer sends its keys into the main session, so use it for parallel follow-ups. If an MCP server exited, retry the tool call—it restarts on the next call instead of failing. A reply cut off mid-stream is discarded instead of running unfinished tool calls, so do not continue from a partial stream.

Suggested actions

1. In the Droid model picker, leave the legacy models toggle off so only current models show; turn it on only when you need a clearly marked older model.
2. On a Droid Computer, set model and autonomy before launch and leave those controls alone while the Computer provisions from a template—the next session now keeps the same model and settings.
3. Start the local Droid session immediately without waiting for the template list; do not refresh Droid Computer templates by hand, they now refresh on their own when they fall out of date.
4. In the Droid terminal, press Alt (Windows/Linux) or Option (macOS) plus the arrow keys to page the session’s full saved history instead of scrolling only the visible buffer.
5. After an MCP server exits, retry the same tool call so Droid restarts it on the next call; if a reply is cut off mid-stream, start a new prompt instead of expecting unfinished tool calls to run.

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/factory-droid-v0-231-0-keep-droid-computer-model-settings-across-launche and mark Applied, Skipped, or Failed. Proposal id: fdaff909-f7ac-4e1c-b2eb-815719786332

Your job

1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.