Woodpecker CI + Memtro

Only when you ask, and only what it has been granted: trigger a pipeline on a branch (it runs the repository's pipeline, which may deploy or publish); restart a finished pipeline (runs it again); cancel a pending or running pipeline; delete a finished pipeline and its logs permanently; approve a pipeline waiting for approval, which starts it; decline a pipeline waiting for approval; create a cron job that runs a branch's pipeline on a schedule; run a cron job's pipeline now; delete a cron job. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

Host and personal access token. In Woodpecker open your avatar → User settings → CLI & API and copy the Personal Access Token. It carries all of its user's rights, so use a dedicated non-admin user with access to just the right repositories, with push access only where Memtro may run pipelines.