{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do I get started?","acceptedAnswer":{"@type":"Answer","text":"Run npx forest-cli@latest start. The CLI asks how you want to run Forest, as a demo project, a standalone back-end or inside your existing app, and sets it up on your data."}},{"@type":"Question","name":"What can I manage from the CLI?","acceptedAnswer":{"@type":"Answer","text":"Projects and environments, role permissions, team layouts, schemas, and layout changes from branch to production. Permissions export to a file you edit and apply after checking the changes."}},{"@type":"Question","name":"Why manage roles from the CLI rather than the UI?","acceptedAnswer":{"@type":"Answer","text":"A file shows every role's permissions side by side. You change them in one place, check the changes and copy the result to another environment. The UI stays there for one-off edits."}},{"@type":"Question","name":"Does the CLI replace the Forest UI?","acceptedAnswer":{"@type":"Answer","text":"No. The CLI is how you set up and configure Forest. Your team then works in the Forest UI, from an LLM client through the MCP server, or in the interfaces you build on the Gateway API."}},{"@type":"Question","name":"Can my AI coding agent use it?","acceptedAnswer":{"@type":"Answer","text":"Yes. The CLI installs the Forest plugin and skills in Claude Code and Codex, so your AI coding agent drafts changes with Forest context. Permission changes still show their diff before they apply."}},{"@type":"Question","name":"Can we run it in our pipeline?","acceptedAnswer":{"@type":"Answer","text":"Yes. The same commands run on a laptop and in CI, and the CLI also ships as a Docker image if you prefer not to install it."}},{"@type":"Question","name":"Why not build this ourselves? AI writes most of it now.","acceptedAnswer":{"@type":"Answer","text":"You can. Coded or vibecoded, a working backoffice takes days now. What AI does not write for you is everything underneath: a permission engine covering humans and AI agents alike, four-eyes approval, and a record-level audit trail that holds up in a regulator's review. That is infrastructure you operate, not code you generate once."}},{"@type":"Question","name":"How do you ensure customer data never leaves our environment?","acceptedAnswer":{"@type":"Answer","text":"The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record."}}]}