Enable streaming terminal responses in Factory Droid
Factory Droid v0.215.0 (Desktop v0.172.0) streams replies and thinking in the terminal, lets you expand running-command output live, and completes MCP sign-in on your machine for local sessions. Turn these on so you see progress immediately and finish local MCP auth without a cloud computer.Why this loop
Waiting for full response blocks and command results hides progress and makes long Droid sessions feel stalled. This release’s terminal setting paints replies and thinking as they arrive, and running commands can be expanded to watch output before the result lands—use both so you can interrupt, redirect, or keep working sooner. Local MCP server sign-in now completes on your own machine for local sessions, which removes a Desktop auth loop when connectors live on localhost. Pair that with clearer BYOK and network errors (provider status code and message; failing host, protocol, and port) so key and connectivity failures are fixed from the message instead of guessed. Ignore payment-onboarding, panel animations, Wiki navigation, and macOS naming; they do not change how you run agent work.
Proposed actions
- Open Factory Droid terminal settings and enable the setting that renders Droid replies and thinking progressively as they arrive instead of waiting for each block to finish.
- In Factory Desktop, expand a running command in the current session so you can watch its output before the result arrives.
- For a local Factory Desktop session, complete MCP server sign-in on this machine (not on a cloud computer) so local MCP servers authenticate in-place.
- On the next BYOK retry failure, capture the provider status code and message Droid now shows and fix the key or provider from that error instead of retrying blindly.
- On the next network error, use the host, protocol, and port named in the message to correct the failing endpoint.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costPaste into Droid / AGENTS.md task
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: Enable streaming terminal responses in Factory Droid Summary: Factory Droid v0.215.0 (Desktop v0.172.0) streams replies and thinking in the terminal, lets you expand running-command output live, and completes MCP sign-in on your machine for local sessions. Turn these on so you see progress immediately and finish local MCP auth without a cloud computer. Primary source: https://docs.factory.ai/changelog/release-notes.md
Why it matters
Waiting for full response blocks and command results hides progress and makes long Droid sessions feel stalled. This release’s terminal setting paints replies and thinking as they arrive, and running commands can be expanded to watch output before the result lands—use both so you can interrupt, redirect, or keep working sooner. Local MCP server sign-in now completes on your own machine for local sessions, which removes a Desktop auth loop when connectors live on localhost. Pair that with clearer BYOK and network errors (provider status code and message; failing host, protocol, and port) so key and connectivity failures are fixed from the message instead of guessed. Ignore payment-onboarding, panel animations, Wiki navigation, and macOS naming; they do not change how you run agent work.
Suggested actions
- Open Factory Droid terminal settings and enable the setting that renders Droid replies and thinking progressively as they arrive instead of waiting for each block to finish.
- In Factory Desktop, expand a running command in the current session so you can watch its output before the result arrives.
- For a local Factory Desktop session, complete MCP server sign-in on this machine (not on a cloud computer) so local MCP servers authenticate in-place.
- On the next BYOK retry failure, capture the provider status code and message Droid now shows and fix the key or provider from that error instead of retrying blindly.
- On the next network error, use the host, protocol, and port named in the message to correct the failing endpoint.
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-215-0-enable-streaming-terminal-responses-in-factory-dr and mark Applied, Skipped, or Failed. Proposal id: b4e50094-2c48-4447-9b07-051dfa4820ba
Your job
- Restate the change in one sentence.
- Propose a minimal plan for my repo (or a throwaway pilot).
- Implement only what I approve; prefer small diffs and tests.
- Call out risks (permissions, breaking APIs, cost).
Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.