Questions

Can the agent push to my main branch?

No. Pushes are allowed to devopsagent/ branches and refused everywhere else. It is an allowlist rather than a list of forbidden names, so a repository whose default branch is called trunk or production is protected the same way. The refusal is tested against a real git remote, including a control proving the same push succeeds without the guard.

What happens when it cannot work out my stack?

It says so. Anything not written down in your repository is reported as unknown rather than guessed at, and where a generated file needed a value anyway, the file carries a comment saying that value was chosen by us and not read from your project.

Are the proposed patches checked before I see them?

Yes. Every patch is run through git apply --check against your actual working copy at the commit it claims. A patch that does not apply is never stored, so no screen can render it. Patches touching .env, key files, or CI permissions are refused outright.

Does it generate Kubernetes manifests?

Only when you ask for them. The default target is a single container with a compose file and a deploy script, because that is what most small teams need. The screen tells you which target produced the files you are looking at.

Does it need write access to my repository?

Not to generate anything. Cloning is read-only over https. A forge token is needed only to open a pull request on your behalf; without one the patch is still generated and verified and you can download the diff, and the interface says so rather than showing a button that cannot work.

What does it cost?

Nothing today. Billing is switched off in this deployment: there is no card form and no page that takes payment. Model usage is metered per call in tenths of a penny and shown on your settings page, so when there is a price you will already know what you were using.

Can it fix any failing build?

No, and it will tell you when it cannot. It reads a log; it does not understand your codebase. Failures that come down to a dependency version, a missing file, a lockfile that is out of date or a wrong command are the ones it handles well. For anything else it will give you a diagnosis and say plainly that it could not write a patch it was sure of.