otty / dotfiles

All tools/Droid

Droid

factory-droid

Use the Droid CLI to run Factory from your terminal, editor, tests, and Git workflow.

Detected by droid | macOS, Linux, Windows |factory.ai

Sync it factory-droid.toml

Sync rules

What travels, what stays, what never leaves

Droid in your home directory Every rule on this page, by file

· settings.json Sync

mcpServers.*.env.*mcpServers.*.headers.*mcpServers.*.oauth.clientSecret

Lifted into your secret store; the rest of the file syncs.

· commands/ Sync

· output-styles/ Sync

· settings.local.json Exclude

· worktrees/ Exclude

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/factory-droid.tomlThe file this page is generated from

id = "factory-droid"

name = "Droid"

homepage = "https://factory.ai"

description = "Use the Droid CLI to run Factory from your terminal, editor, tests, and Git workflow."

# Factory's own mark, the SVG favicon its site serves.

icon = "https://factory.ai/favicon.svg"

detect = ["droid"]

# https://docs.factory.ai/cli/configuration/settings names the user-level

# settings file: "~/.factory/settings.json" on macOS and Linux,

# "%USERPROFILE%\.factory\settings.json" on Windows — the same path, since a

# Windows user profile root is the home directory, so it is written once.

# The page's example holds model, reasoningEffort, outputStyle, diffMode and

# the notification sounds, and also names ~/.factory/output-styles/ as the

# directory custom output styles are discovered in.

# https://docs.factory.ai/cli/configuration/mcp: MCP servers are configured

# at three levels, the user-level one being "~/.factory/mcp.json".

# https://docs.factory.ai/cli/configuration/custom-commands: personal slash

# commands live in "~/.factory/commands" — "Private or cross-project

# shortcuts available across sessions".

paths = [

"~/.factory/settings.json",

"~/.factory/mcp.json",

"~/.factory/commands/",

"~/.factory/output-styles/",

]

# The settings page calls settings.local.json "machine-specific overrides",

# which is the file's whole purpose: it exists so that what is in it stays on

# one machine. ~/.factory/worktrees is the default parent directory for git

# worktrees droid creates — checkouts, not configuration.

exclude = [

"~/.factory/settings.local.json",

"~/.factory/worktrees/",

]

# No whole-file credential is documented under ~/.factory: the MCP page says

# OAuth tokens are held in the system keyring rather than on disk, and the

# files named above are settings and command definitions.

secret = []

# The MCP page is explicit that credentials do not belong in mcp.json —

# "Never put secrets there: header auth tokens (such as `Authorization`),

# `oauth.clientSecret`, or API keys" — and offers ${NAME} expansion instead.

# A rule is still worth having, because the file is exactly where an inlined

# token ends up when someone skips that advice, and syncing it would carry the

# token in the clear. The three key paths are the three places the page says a

# credential can appear: the stdio server's env block, the http/sse server's

# headers, and the OAuth client secret.

[[secret_paths]]

file = "~/.factory/mcp.json"

match = { key_path = [

"mcpServers.*.env.*",

"mcpServers.*.headers.*",

"mcpServers.*.oauth.clientSecret",

] }

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/factory-droid. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page.