Paste 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: Set BYOK custom models as managed defaults for sessions and subagents
Summary: Factory Droid v0.199.0 lets org admins pick BYOK models as managed defaults for sessions and subagents, persist TypeScript SDK system prompts across resumes, and give explorer every read-only tool (commands, web search, MCP). Lock models and use explorer for read-only work.
Primary source: https://docs.factory.ai/changelog/release-notes.md

## Why it matters
v0.199.0 makes model choice an org default instead of a per-session guess: Enterprise Controls can now set BYOK custom models as managed defaults for sessions and subagents, and service accounts finally appear in model policies so automation can be limited to approved models. The TypeScript SDK can set a custom system prompt that is kept when the session resumes, so coding standards no longer drop on reconnect. Missions can pick models and reasoning defaults in their own settings. The explorer droid can now use every read-only tool—command execution, web search, and MCP—while file edits stay blocked, which is the right shape for investigation. Question prompts also gained Space/number/Tab controls and keep agent context visible, so answering is faster. Adopt the defaults and explorer path now so new sessions, subagents, and service accounts inherit the approved stack.

## Suggested actions
1. In Factory Enterprise Controls, pick our BYOK custom model as the managed default for new sessions and for subagents.
2. In Enterprise Controls model policies, add each service account and set the exact models that account may use.
3. In the Factory TypeScript SDK, set a custom system prompt when creating the session (team coding standards and repo constraints) and resume the same session to confirm the prompt is still applied.
4. Open the mission in the Factory app, go to Mission settings, and choose the models and reasoning defaults that mission should use before launching it.
5. Start the built-in explorer droid and instruct it: use every read-only tool you have—command execution, web search, and MCP tools—to investigate; do not edit files.

## Config surfaces this release may change
- subagent definitions — check your repo before applying


## 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.