Fork Factory Droid sessions from the session-list sidebar
Factory Droid v0.223.0 (Desktop v0.180.0) adds sidebar session forking, PyCharm as an editor target, org-managed Databricks, hook rewrite risk-level preservation, and a new medium default autonomy. Fork instead of restarting, and set autonomy explicitly.Why this loop
Sidebar forking is the highest-leverage workflow change: you can branch a session from its row in the session list without discarding the original. Pair that with opening session files in PyCharm from the editor menu so the forked work stays in your IDE. Hooks that rewrite a command can now keep the original risk level, which matters because more disk-write commands require confirmation before Droid runs them—do not let a rewrite drop that gate. Sessions now default to medium autonomy instead of off when none is chosen, so unattended or high-risk work must set autonomy explicitly. Admins should configure the organization-managed Databricks connector so members authenticate with their own accounts. Custom-model credential failures now surface at session start; treat that notice as a hard stop before relying on a custom model.
Proposed actions
- Upgrade Factory Droid to v0.223.0 (Desktop v0.180.0), then fork this session from its row in the session-list sidebar so the original history stays intact while we try a parallel approach.
- From the editor menu, open this session's files in PyCharm instead of copying paths into another IDE.
- Set rewritten-command hooks to keep the existing risk level so disk-write commands still require confirmation after the hook rewrites them.
- Do not rely on autonomy being off: set this session's autonomy explicitly (off for unattended or high-risk runs) because new sessions now default to medium.
- Administrators: set up the organization-managed Databricks connector so each member connects with their own Databricks account rather than a shared credential.
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: Fork Factory Droid sessions from the session-list sidebar Summary: Factory Droid v0.223.0 (Desktop v0.180.0) adds sidebar session forking, PyCharm as an editor target, org-managed Databricks, hook rewrite risk-level preservation, and a new medium default autonomy. Fork instead of restarting, and set autonomy explicitly. Primary source: https://docs.factory.ai/changelog/release-notes.md
Why it matters
Sidebar forking is the highest-leverage workflow change: you can branch a session from its row in the session list without discarding the original. Pair that with opening session files in PyCharm from the editor menu so the forked work stays in your IDE. Hooks that rewrite a command can now keep the original risk level, which matters because more disk-write commands require confirmation before Droid runs them—do not let a rewrite drop that gate. Sessions now default to medium autonomy instead of off when none is chosen, so unattended or high-risk work must set autonomy explicitly. Admins should configure the organization-managed Databricks connector so members authenticate with their own accounts. Custom-model credential failures now surface at session start; treat that notice as a hard stop before relying on a custom model.
Suggested actions
- Upgrade Factory Droid to v0.223.0 (Desktop v0.180.0), then fork this session from its row in the session-list sidebar so the original history stays intact while we try a parallel approach.
- From the editor menu, open this session's files in PyCharm instead of copying paths into another IDE.
- Set rewritten-command hooks to keep the existing risk level so disk-write commands still require confirmation after the hook rewrites them.
- Do not rely on autonomy being off: set this session's autonomy explicitly (off for unattended or high-risk runs) because new sessions now default to medium.
- Administrators: set up the organization-managed Databricks connector so each member connects with their own Databricks account rather than a shared credential.
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-223-0-fork-factory-droid-sessions-from-the-session-list and mark Applied, Skipped, or Failed. Proposal id: d8f1df48-6798-48e8-a5b9-07f3324f266d
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.