Resources
Frequently asked questions
Answers to common developer, platform, and rollout questions when adopting Refactor across teams.
Can we start without changing existing PR workflows?
Yes. Start in pr_only mode and keep your normal repository review and merge process unchanged. Refactor augments your workflow with run artifacts and policy checks.
Do developers need provider keys for every run?
No for hosted cloud-managed workflows. External developers should authenticate with the developer key issued in ReactorAI. Provider keys are only needed when your team explicitly chooses a BYOK local mode.
How do we enforce release controls across multiple teams?
Use project-level governance defaults: required approver roles, protected branches, and strict gate evaluation. These controls block publish when policy is not satisfied.
How should we roll out adoption?
- Start with one pilot repository and baseline policies.
- Measure cycle time reduction and blocked publish reasons.
- Promote templates and onboarding scripts to adjacent teams.
- Standardize security and governance checks in CI.
How do I debug access and publish outcomes quickly?
Identity and session checks
export REFACTOR_PLATFORM_URL=https://reactorai.codes
refactor whoami
refactor status
refactor config