jules
Create and manage Google Jules AI coding sessions via the Jules REST API. Start tasks, monitor progress, approve plans, send messages, list sources/repos, and retrieve session activities/artifacts.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- jules
- metadata
- { "openclaw": { "emoji": "🤖", "homepage": "https://jules.google/docs/api/reference/", "requires": { "env": [ "JULES_API_KEY" ], "bins": [ "curl" ] }, "primaryEnv": "JULES_API_KEY" } }
- description
- Create and manage Google Jules AI coding sessions via the Jules REST API. Start tasks, monitor progress, approve plans, send messages, list sources/repos, and retrieve session activities/artifacts.
03 SKILL.md 正文
Jules API Skill
Interact with the Google Jules AI coding agent via its REST API. Jules can autonomously execute coding tasks on your GitHub repositories — writing code, fixing bugs, adding tests, and creating pull requests.
Base URL: https://jules.googleapis.com/v1alpha
Auth: Pass your API key via the x-goog-api-key header. Get one at jules.google.com/settings.
List Sources (Connected Repositories)
Discover which GitHub repos are connected to your Jules account:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sources?pageSize=30"
With pagination:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sources?pageSize=10&pageToken=PAGE_TOKEN"
Filter specific sources:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sources?filter=name%3Dsources%2Fgithub-owner-repo"
Get a Source
Get details and branches for a specific repo:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sources/SOURCE_ID"
Example: sources/github-myorg-myrepo — replace with your actual source ID from List Sources.
Create a Session (Start a Coding Task)
Create a new Jules session to execute a coding task on a repo:
curl -s -X POST \
-H "x-goog-api-key: $JULES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "TASK_DESCRIPTION",
"title": "OPTIONAL_TITLE",
"sourceContext": {
"source": "sources/github-OWNER-REPO",
"githubRepoContext": {
"startingBranch": "main"
}
},
"requirePlanApproval": true
}' \
"https://jules.googleapis.com/v1alpha/sessions"
Parameters
| Parameter | Required | Description |
|---|---|---|
prompt |
Yes | The task description for Jules to execute |
title |
No | Optional title (auto-generated if omitted) |
sourceContext.source |
Yes | Source resource name (e.g. sources/github-owner-repo) |
sourceContext.githubRepoContext.startingBranch |
Yes | Branch to start from (e.g. main, develop) |
requirePlanApproval |
No | If true, plans need explicit approval before execution |
automationMode |
No | Set to AUTO_CREATE_PR to auto-create PRs when done |
Auto-approve + Auto-PR example
curl -s -X POST \
-H "x-goog-api-key: $JULES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "Add comprehensive unit tests for the auth module",
"sourceContext": {
"source": "sources/github-myorg-myrepo",
"githubRepoContext": { "startingBranch": "main" }
},
"automationMode": "AUTO_CREATE_PR"
}' \
"https://jules.googleapis.com/v1alpha/sessions"
List Sessions
List all your Jules sessions:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions?pageSize=10"
Paginate with pageToken:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions?pageSize=10&pageToken=NEXT_PAGE_TOKEN"
Get a Session
Retrieve a single session by ID (includes outputs like PRs if completed):
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID"
Session States
| State | Meaning |
|---|---|
QUEUED |
Waiting to be processed |
PLANNING |
Jules is analyzing and creating a plan |
AWAITING_PLAN_APPROVAL |
Plan ready, waiting for user approval |
AWAITING_USER_FEEDBACK |
Jules needs additional input |
IN_PROGRESS |
Jules is actively working |
PAUSED |
Session is paused |
COMPLETED |
Task completed successfully |
FAILED |
Task failed to complete |
Approve a Plan
When a session is in AWAITING_PLAN_APPROVAL state, approve the plan:
curl -s -X POST \
-H "x-goog-api-key: $JULES_API_KEY" \
-H "Content-Type: application/json" \
-d '{}' \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID:approvePlan"
Send a Message
Send feedback, answer questions, or give additional instructions to an active session:
curl -s -X POST \
-H "x-goog-api-key: $JULES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "YOUR_MESSAGE_HERE"
}' \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID:sendMessage"
Use this when session state is AWAITING_USER_FEEDBACK or to provide additional guidance during IN_PROGRESS.
List Activities (Monitor Progress)
Get all events/progress for a session:
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID/activities?pageSize=50"
Get activities after a specific timestamp (for polling):
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID/activities?createTime=2026-01-17T00:03:53Z"
Activity Types
Activities will contain exactly one of these event fields:
| Event | Description |
|---|---|
planGenerated |
Jules created a plan (contains plan.steps[]) |
planApproved |
A plan was approved |
userMessaged |
User sent a message |
agentMessaged |
Jules sent a message |
progressUpdated |
Status update during execution |
sessionCompleted |
Session finished successfully |
sessionFailed |
Session encountered an error (contains reason) |
Artifacts
Activities may include artifacts:
- ChangeSet: Code changes with
gitPatch(unified diff, base commit, suggested commit message) - BashOutput: Command output with
command,output,exitCode - Media: Binary output with
mimeTypeand base64data
Get a Single Activity
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID/activities/ACTIVITY_ID"
Delete a Session
curl -s -X DELETE \
-H "x-goog-api-key: $JULES_API_KEY" \
"https://jules.googleapis.com/v1alpha/sessions/SESSION_ID"
Typical Workflow
- List sources to find the repo resource name
- Create a session with a prompt describing the task
- Poll the session (Get Session) to track state changes
- List activities to monitor progress and read Jules' messages
- If
requirePlanApprovalwas set, approve the plan when state isAWAITING_PLAN_APPROVAL - If state is
AWAITING_USER_FEEDBACK, send a message with your response - When
COMPLETED, get the session to find the output PR URL
Error Handling
| Code | Meaning |
|---|---|
| 200 | Success |
| 400 | Bad request (invalid parameters) |
| 401 | Unauthorized (invalid/missing API key) |
| 403 | Forbidden (insufficient permissions) |
| 404 | Not found |
| 429 | Rate limited |
| 500 | Server error |
Error responses return:
{
"error": {
"code": 400,
"message": "Invalid session ID format",
"status": "INVALID_ARGUMENT"
}
}
Notes
- Get your API key from jules.google.com/settings
- Store it as the
JULES_API_KEYenvironment variable - Sources (repos) are connected via the Jules web UI at jules.google — the API is read-only for sources
- Session resource names follow the pattern
sessions/{sessionId} - Activity resource names follow
sessions/{sessionId}/activities/{activityId} - All list endpoints support
pageSize(1-100) andpageTokenfor pagination
04 同仓库更多 Skills
crowd-prompting
A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.
ceaser
Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
ceaser-send
Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir/UltraHonk zero-knowledge proofs.
dilemm-ai
Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
arxiv-paper-reviews
Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.