fallow recommend inspects the project (frameworks, workspace layout, tooling) and emits three things: what it detected, a safe proposed config, and the list of decisions behind that proposal, so a human or an agent can review the reasoning instead of trusting a generated file.
Zero config is a valid stop: fallow’s defaults are strong, so writing no config at all is fully supported.
recommend exists for the projects that do want one, and for agents that need to author it with the user instead of guessing.fallow init, which writes a config file, recommend is read-only. The intended flow for agents: run recommend --format json, apply the auto decisions, disclose the default decisions, ask the user about the taste decisions, then write the result (or run init).
Decision tiers
Every proposed setting comes with its tier and rationale:Options
Global flags such as
--no-cache and --threads also apply; see global flags.
JSON output
detected block also reports monorepo workspace patterns, the workspace tool, Storybook presence, and whether frameworks live in workspace packages rather than the root.
Related
fallow initwrites the config file (and can scaffoldAGENTS.mdand git hooks)fallow config-schemaprints the full JSON schema for every config key- The MCP server exposes this command as the read-only
recommendtool; see MCP integration