Langy is not available in my org
Langy is not available in my org
- Cloud: Langy is available. Open the panel to get started.
- Self-hosted: the agent pod deploys by default. Confirm it was not disabled (
langyagent.chartManaged=false) and the pod is running. A running pod is not the whole story: withenableForAllUsers: falsethe install keeps the rollout flag authoritative, so Langy stays dark until you target the projects or organizations you want. See Self-hosting overview and Setup.
Langy can't open a PR
Langy can't open a PR
Two common causes.
- The GitHub App is not installed. Langy opens pull requests only on repositories where its GitHub App is installed. When it reaches for
gitorghand no install exists, it stops the turn and shows an Install card in chat. Use that card to install the app, then re-run the turn. See GitHub access. - Outbound HTTPS is off (self-hosted). A hardened install with
networkPolicy.allowExternalHttpsset tofalseblocksgithub.com,api.github.com, andcodeload.github.com. Allow those FQDNs (or turnallowExternalHttpson) so the worker can push and open the PR. See Networking and egress. - Also check you are under the daily PR cap. Langy opens at most 20 pull requests per project per day. See Limits.
Langy has no model
Langy has no model
Langy runs on the providers your project has enabled, and there is no default key. Configure a provider (paste an API key) or sign in with your OpenAI account for Codex. Until a model is available for the Langy role, Langy cannot run a turn. See Supported models and Codex.
A turn was stopped
A turn was stopped
You can stop a running turn for real, and you can continue or resume afterward. A stop is an intentional outcome, not a failure: Langy keeps the partial answer streamed so far, and nothing you did is wrong. Continue the conversation, or ask again. A refresh mid-turn rejoins the running turn rather than losing it.
Langy's worker stopped mid-reply
Langy's worker stopped mid-reply
If a worker process dies mid-reply, Langy surfaces a “worker stopped” card. Your message is safe. Send it again; a fresh worker spawns for the next turn.
Audit-log events to check
When Langy touches GitHub, it writes audit-log events. Use these to confirm what happened and when.Also check: GitHub access, Limits, Supported models.