Settings

App status

Your password

Changing the password signs out your other sessions. Scripts keep using Authorization: Bearer.

People

Named accounts share every project. Admins can add or remove people. Per-project permissions are not implemented yet. Scripts still use the instance Bearer token.

Only admins can add or remove accounts.

Rebuild images

API and PWA are compiled images (the frontend has no source mount). Neither api nor grok gets docker.sock. Rebuild writes a drop-box file ($DEVELESCENT_HOME/control/rebuild.request, or var/rebuild.request on the host-Grok override). Grok can run request-rebuild.sh api|frontend|grok. Host path unit: sudo ./scripts/install-rebuild-service.sh.

Grok bridge is not connected. From deploy/: docker compose up -d grok, then docker compose run --rm -it grok auth if needed.

Forge credentials

Shared across all projects for private clone, push, and publish. Secrets encrypted at rest; only label/provider shown after save. The API and Grok containers do not mount host SSH keys — HTTPS remotes plus a stored PAT are required. After one credential is saved, Grok can request develescent-query.sh git-push (token never leaves the API). To copy tokens that already live on the host (git credential helper / gh / env), run ./scripts/import-host-git-credentials.sh on the host — not inside compose Grok. SSH keys are not imported.

Add credential

App passwords are deprecated. Create an Atlassian API token with Bitbucket scopes (Account → Security → API tokens). Store your Atlassian email as username (REST APIs). Git push automatically uses x-bitbucket-api-token-auth — email as the git username is rejected by Bitbucket. Required scopes include read:repository:bitbucket and write:repository:bitbucket.

Clone onboard

Clone an HTTPS repository under REPOS_DIR and register a new project. The API chowns the tree to the host user (HOST_UID) so Grok Build can edit on the host. Edit the display name afterward on Project.