JernCloudStart with GitHubJern Cloud docs
Turn an issue into a pull request with a label.
Work starts where it is asked for. A label on an issue opens a session whose first message is the issue itself, and Jern Cloud answers on the issue with a link.
- Getting started
- Sessions
- Policy
- Triggers
- Schedules
- Skills
- Environments
- Browser
- Memory
- Knowledge
- Receipts
- Spend
- Provider keys
- Settings
- MCP server
- Recipes
- FAQ and limits
The setup
Triggers on under Settings › Triggers, with a model for triggered sessions and the default label, jern. The person who adds the label must have signed in to Jern Cloud and have write access to the repository; the session runs as them, under the workspace's approval requirement, limits, and provider keys.
The issue
Issue 43, titled "Document functions", with a one-line body. The label went on; the session's first message became the title, the body, and a line saying which issue and who labelled it.
What came back
A comment on the issue within seconds: "Jern Cloud started a session for this issue", with the link, and then pull request 68, since merged. The agent read the issue through the run-scoped MCP server, which the receipt records, added the docstring the issue asked for, ran the tests, and referenced the issue in the pull request.
| Receipt row | What it said |
|---|---|
| Outcome | success, pull request ready |
| Policy | .jern/baseline.json digest 5a58da65014e, repository baseline, pinned |
| Model | 5 gateway calls |
| Tokens | 30,779 in, 1,082 out; 10,396 counted toward the cap |
| Estimated spend | $0.014 at list price |
| Files touched | src/temperature.py +1 −0; 1 of at most 4 files, 1 of at most 200 lines |
| Issues | #43 read through the run-scoped MCP server |
| Network | docs.python.org allowed; none contacted |
What the agent could not do
Comment, label, close, or merge. It holds no GitHub credential; it reads the issue through a tool the receipt lists, and the runner publishes the branch and opens the pull request with a credential the agent never sees. If the label goes on and nothing can start, the trial has ended, the model has no key, the concurrency is used up, Jern Cloud says so on the issue and the workspace is notified.
Try it on your repository
- Turn triggers on and choose the model. Keep the default label or name your own.
- Write the issue as you would for a colleague: what, where, and how you will know it is done.
- Add the label. Follow the link in the comment, or wait for the pull request and its receipt check.