skills$openclaw/jules-api
sanjacob992.4k

by sanjacob99

jules-api – OpenClaw Skill

jules-api is an OpenClaw Skills integration for coding workflows. Use the Jules REST API (v1alpha) via curl to list sources, create sessions, monitor activities, approve plans, send messages, and retrieve outputs (e.g., PR URLs). Use when the user wants to delegate coding tasks to Jules programmatically.

2.4k stars7.8k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026coding

Skill Snapshot

namejules-api
descriptionUse the Jules REST API (v1alpha) via curl to list sources, create sessions, monitor activities, approve plans, send messages, and retrieve outputs (e.g., PR URLs). Use when the user wants to delegate coding tasks to Jules programmatically. OpenClaw Skills integration.
ownersanjacob99
repositorysanjacob99/jules-and-lobster
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @sanjacob99/jules-and-lobster
last updatedFeb 7, 2026

Maintainer

sanjacob99

sanjacob99

Maintains jules-api in the OpenClaw Skills directory.

View GitHub profile
File Explorer
5 files
.
scripts
jules_api.sh
3.6 KB
jules.js
1.9 KB
_meta.json
472 B
SKILL.md
16.1 KB
SKILL.md

name: jules-api description: "Use the Jules REST API (v1alpha) via curl to list sources, create sessions, monitor activities, approve plans, send messages, and retrieve outputs (e.g., PR URLs). Use when the user wants to delegate coding tasks to Jules programmatically."

Jules REST API Skill

Quick Start

# 1. Verify available sources (pre-flight check)
./scripts/jules_api.sh sources

# 2. Create a session with auto PR creation
./scripts/jules_api.sh new-session \
  --source "sources/github/OWNER/REPO" \
  --title "Add unit tests" \
  --prompt "Add comprehensive unit tests for the authentication module" \
  --branch main \
  --auto-pr

# 3. Monitor session progress
./scripts/jules_api.sh activities --session SESSION_ID

Note: Use your GitHub username/org, not your local system username (e.g., sources/github/octocat/Hello-World, not sources/github/$USER/Hello-World).

Overview

This skill enables programmatic interaction with the Jules REST API (v1alpha) for delegating coding tasks to Jules, Google's autonomous AI coding agent. It supports:

  • Task Assignment: Create new coding sessions with specific prompts
  • Session Monitoring: Track session state and activities in real-time
  • Plan Management: Approve or review generated plans
  • Messaging: Send follow-up messages to active sessions
  • Result Integration: Retrieve PR URLs and code changes from completed sessions

Before You Start

1. Get an API Key

Create a Jules API key in the Jules web app:

Export it on the machine running the agent:

export JULES_API_KEY="your-api-key-here"

2. Connect Your GitHub Repository

Before the API can operate on a GitHub repo, you must:

  1. Install the Jules GitHub app via the Jules web UI
  2. Grant access to the specific repositories you want Jules to work on

3. Verify Repository Access

# List available sources to verify access and see correct format
./scripts/jules_api.sh sources

You'll see entries like:

{
  "sources": [
    {
      "name": "sources/github/octocat/Hello-World",
      "githubRepo": {
        "owner": "octocat",
        "repo": "Hello-World",
        "defaultBranch": { "displayName": "main" },
        "branches": [
          { "displayName": "main" },
          { "displayName": "develop" }
        ]
      }
    }
  ]
}

Base URL & Authentication

PropertyValue
Base URLhttps://jules.googleapis.com/v1alpha
Auth Headerx-goog-api-key: $JULES_API_KEY

All requests authenticate with:

-H "x-goog-api-key: $JULES_API_KEY"

Core Concepts

Resources

ResourceDescription
SourceA GitHub repository connected to Jules. Format: sources/github/{owner}/{repo}
SessionA unit of work where Jules executes a coding task. Contains state, activities, and outputs
ActivityAn individual event within a session (plan generated, message sent, progress update, etc.)

Session States

StateDescription
QUEUEDSession is waiting to start
PLANNINGGenerating execution plan
AWAITING_PLAN_APPROVALWaiting for user to approve plan
AWAITING_USER_FEEDBACKNeeds user input to continue
IN_PROGRESSActively executing the task
PAUSEDTemporarily stopped
COMPLETEDSuccessfully finished
FAILEDEncountered an error

Activity Types

TypeDescription
Plan GeneratedA plan was generated for the task
Plan ApprovedThe plan was approved (manually or auto)
User MessageUser posted a message to the session
Agent MessageJules posted a message
Progress UpdateStatus update on current work
Session CompletedSession finished successfully
Session FailedSession encountered an error

Option 1: Automated Session with Auto-PR (Recommended)

Create a session that automatically creates a PR when complete:

./scripts/jules_api.sh new-session \
  --source "sources/github/octocat/Hello-World" \
  --title "Fix login bug" \
  --prompt "Fix the null pointer exception in the login handler when email is empty" \
  --branch main \
  --auto-pr

Why this is recommended:

  • Plans are automatically approved (default behavior)
  • PR is created automatically on completion
  • Minimal manual intervention required

Option 2: Session with Plan Approval

For sensitive operations, require explicit plan approval:

# Create session requiring plan approval
./scripts/jules_api.sh new-session \
  --source "sources/github/octocat/Hello-World" \
  --title "Refactor auth module" \
  --prompt "Refactor the authentication module to use OAuth2" \
  --branch main \
  --require-plan-approval \
  --auto-pr

# Monitor until AWAITING_PLAN_APPROVAL state
./scripts/jules_api.sh activities --session SESSION_ID

# Review the plan, then approve
./scripts/jules_api.sh approve-plan --session SESSION_ID

Option 3: Interactive Session

Send follow-up messages during an active session:

# Create session
./scripts/jules_api.sh new-session \
  --source "sources/github/octocat/Hello-World" \
  --title "Add API endpoints" \
  --prompt "Add REST API endpoints for user management" \
  --branch main

# Send additional instructions
./scripts/jules_api.sh send-message \
  --session SESSION_ID \
  --prompt "Also add input validation for all endpoints"

API Reference

Sources

List Sources

Lists all connected GitHub repositories.

curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sources"

Query Parameters:

ParameterTypeDefaultDescription
pageSizeinteger30Number of sources to return (1-100)
pageTokenstring-Token from previous response for pagination
filterstring-AIP-160 filter (e.g., name=sources/source1)

Response:

{
  "sources": [
    {
      "name": "sources/github/octocat/Hello-World",
      "githubRepo": {
        "owner": "octocat",
        "repo": "Hello-World",
        "isPrivate": false,
        "defaultBranch": { "displayName": "main" },
        "branches": [
          { "displayName": "main" },
          { "displayName": "develop" }
        ]
      }
    }
  ],
  "nextPageToken": "..."
}
Get Source

Retrieves a single source by name.

curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sources/github/octocat/Hello-World"

Use this to see available branches before creating a session.


Sessions

Create Session

Creates a new coding session.

curl -sS "https://jules.googleapis.com/v1alpha/sessions" \
  -X POST \
  -H "Content-Type: application/json" \
  -H "x-goog-api-key: $JULES_API_KEY" \
  -d '{
    "prompt": "Add unit tests for the login module",
    "title": "Add Login Tests",
    "sourceContext": {
      "source": "sources/github/octocat/Hello-World",
      "githubRepoContext": {
        "startingBranch": "main"
      }
    },
    "requirePlanApproval": false,
    "automationMode": "AUTO_CREATE_PR"
  }'

Request Body Fields:

FieldTypeRequiredDescription
promptstringYesThe task description for Jules
titlestringNoShort title for the session
sourceContext.sourcestringYesSource name (e.g., sources/github/owner/repo)
sourceContext.githubRepoContext.startingBranchstringYesBranch to start from
requirePlanApprovalbooleanNoIf true, pause for plan approval (default: false)
automationModestringNoSet to AUTO_CREATE_PR for automatic PR creation

Response:

{
  "name": "sessions/31415926535897932384",
  "id": "31415926535897932384",
  "prompt": "Add unit tests for the login module",
  "title": "Add Login Tests",
  "state": "QUEUED",
  "url": "https://jules.google/session/31415926535897932384",
  "createTime": "2026-01-15T10:30:00Z",
  "updateTime": "2026-01-15T10:30:00Z"
}
List Sessions

Lists your sessions.

curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions?pageSize=20"

Query Parameters:

ParameterTypeDefaultDescription
pageSizeinteger30Number of sessions to return (1-100)
pageTokenstring-Token from previous response for pagination
Get Session

Retrieves a single session by ID.

curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID"

Response includes outputs on completion:

{
  "name": "sessions/31415926535897932384",
  "id": "31415926535897932384",
  "state": "COMPLETED",
  "outputs": [
    {
      "pullRequest": {
        "url": "https://github.com/octocat/Hello-World/pull/42",
        "title": "Add Login Tests",
        "description": "This PR adds comprehensive unit tests..."
      }
    }
  ]
}
Send Message

Sends a message to an active session.

curl -sS \
  -X POST \
  -H "Content-Type: application/json" \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID:sendMessage" \
  -d '{"prompt": "Also add integration tests"}'

Use this to provide feedback, answer questions, or give additional instructions.

Approve Plan

Approves a pending plan (only needed if requirePlanApproval was true).

curl -sS \
  -X POST \
  -H "Content-Type: application/json" \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID:approvePlan"
Delete Session

Deletes a session.

curl -sS \
  -X DELETE \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID"

Activities

List Activities

Lists activities for a session.

curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID/activities?pageSize=30"

Query Parameters:

ParameterTypeDefaultDescription
pageSizeinteger50Number of activities to return (1-100)
pageTokenstring-Token from previous response for pagination

Response:

{
  "activities": [
    {
      "name": "sessions/123/activities/456",
      "createTime": "2026-01-15T10:31:00Z",
      "planGenerated": {
        "plan": "1. Analyze existing code\n2. Create test files\n3. Write tests..."
      }
    },
    {
      "name": "sessions/123/activities/457",
      "createTime": "2026-01-15T10:32:00Z",
      "progressUpdate": {
        "title": "Writing tests",
        "details": "Creating test file for auth module..."
      }
    }
  ],
  "nextPageToken": "..."
}

Activities may include artifacts with code changes:

{
  "artifacts": [
    {
      "changeSet": {
        "gitPatch": {
          "unidiffPatch": "diff --git a/...",
          "baseCommitId": "abc123",
          "suggestedCommitMessage": "Add unit tests for login"
        }
      }
    }
  ]
}
Get Activity

Retrieves a single activity by ID.

curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID/activities/ACTIVITY_ID"

Script Reference

jules_api.sh

The scripts/jules_api.sh script provides a convenient wrapper for common API operations.

Usage:

# List sources
./scripts/jules_api.sh sources

# List sessions
./scripts/jules_api.sh sessions [--page-size N]

# List activities for a session
./scripts/jules_api.sh activities --session <id> [--page-size N]

# Send message to session
./scripts/jules_api.sh send-message --session <id> --prompt "..."

# Approve plan
./scripts/jules_api.sh approve-plan --session <id>

# Create new session
./scripts/jules_api.sh new-session \
  --source "sources/github/owner/repo" \
  --title "..." \
  --prompt "..." \
  [--branch main] \
  [--auto-pr] \
  [--require-plan-approval]

Flags:

FlagDescription
--sourceSource name (format: sources/github/owner/repo)
--titleSession title
--promptTask description or message content
--sessionSession ID
--branchStarting branch (default: main)
--auto-prEnable automatic PR creation
--require-plan-approvalRequire explicit plan approval
--page-sizeNumber of results to return

jules.js

The scripts/jules.js script wraps the Jules CLI for programmatic use.

Usage:

node scripts/jules.js version
node scripts/jules.js list-repos
node scripts/jules.js list-sessions
node scripts/jules.js new --repo owner/repo --task "Your task"
node scripts/jules.js pull --session SESSION_ID

Common Error Patterns

"Source not found" or "Repository not found"

Cause: Repository not connected or incorrect source name format.

Solution:

  1. Run ./scripts/jules_api.sh sources to list available sources
  2. Ensure you've installed the Jules GitHub app for this repo
  3. Use the exact source name from the list (e.g., sources/github/octocat/Hello-World)

"Missing JULES_API_KEY"

Cause: API key not set in environment.

Solution:

export JULES_API_KEY="your-api-key"

Authentication Errors

Cause: Invalid or expired API key.

Solution:

  1. Generate a new API key at https://jules.google.com/settings#api
  2. Update the JULES_API_KEY environment variable
  3. Note: You can have at most 3 API keys at a time

Session Stuck in AWAITING_PLAN_APPROVAL

Cause: Session was created with requirePlanApproval: true.

Solution:

./scripts/jules_api.sh approve-plan --session SESSION_ID

Task Fails with Vague Error

Cause: Vague prompts may produce unexpected results.

Solution:

  • Write clear, specific prompts
  • Break large tasks into smaller, focused tasks
  • Avoid prompts that require long-running commands (dev servers, watch scripts)

Large Files Skipped

Cause: Files exceeding 768,000 tokens may be skipped.

Solution:

  • Break down operations on very large files
  • Consider splitting large files before processing

Best Practices

Writing Effective Prompts

  1. Be specific: Instead of "fix the bug", say "fix the null pointer exception in auth.js:45 when email is undefined"
  2. Provide context: Mention relevant files, functions, or error messages
  3. Keep tasks focused: One logical task per session

Monitoring Sessions

  1. Poll session state to track progress
  2. Check activities for detailed progress updates
  3. Handle AWAITING_USER_FEEDBACK state by sending clarifying messages

Security

  1. Never include secrets or credentials in prompts
  2. Review generated PRs before merging
  3. Use requirePlanApproval: true for sensitive operations

Performance

  1. Use automationMode: AUTO_CREATE_PR for streamlined workflows
  2. Let plans auto-approve for routine tasks
  3. Break complex tasks into smaller sessions

Extracting Results

When a session completes, retrieve the PR URL from outputs:

# Get session details
curl -sS \
  -H "x-goog-api-key: $JULES_API_KEY" \
  "https://jules.googleapis.com/v1alpha/sessions/SESSION_ID" \
  | jq '.outputs[].pullRequest.url'

Known Limitations

  • Alpha API: Specifications may change; API keys and definitions are experimental
  • No long-running commands: Jules cannot run npm run dev or similar watch scripts
  • Context size: Files > 768,000 tokens may be skipped
  • Prompt sensitivity: Vague prompts may produce unexpected results

References

README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

1. Never include secrets or credentials in prompts 2. Review generated PRs before merging 3. Use `requirePlanApproval: true` for sensitive operations

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install jules-api?

Run openclaw add @sanjacob99/jules-and-lobster in your terminal. This installs jules-api into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/sanjacob99/jules-and-lobster. Review commits and README documentation before installing.