5wpr icon5wprSep 30, 2026 ~7 min source read

Jules in Public Relations: A 2026 Practitioner Guide

How comms teams can use Google’s Jules autonomous coding agent to build and maintain small internal tools via a GitHub workflow, what setup is required, and a practical example of deployment.

Jules in Public Relations: The 2026 Practitioner Guide

Share this story

Send the public story page.

Useful takeaways from this story.

Jules is an autonomous coding agent that clones a repo, plans multi-file changes, executes them in a cloud VM, and opens a pull request for review.

Jules runs on Gemini models and offers tiered daily task limits: free (15), Pro (100), and Ultra (300) tasks per day, per the product site.

Because Jules writes a readable step-by-step plan before making changes, non-developers can assign tasks and review or edit the plan before code is executed.

# What Jules does for PR teams Jules is Google's autonomous coding agent introduced as a Google Labs project in December 2024. It clones a target repository into an isolated cloud virtual machine, writes a plan for the requested change, executes multi-file updates, and opens a pull request ready for review. The workflow hands back a finished PR rather than requiring someone to watch an interactive session, which aligns with how engineering teams often work.

# Why communicators would use Jules Comms teams typically need small internal tools: newsroom archives, media-monitoring trackers, approval-routing pages, and link-checking scripts. Those are the same kinds of tasks Jules is built to handle. A non-developer can create a clear GitHub issue describing the desired change, assign it to Jules, then review the resulting pull request when the agent finishes.

# Practical setup requirements

  • A GitHub repository already hosting the internal tool codebase. Jules operates through repository access and the issue-to-PR workflow.
  • A process for issuing and assigning GitHub issues so the task is clear and actionable.
  • A reviewer who will inspect Jules' pre-execution plan and the resulting PR before merging.

# Example workflow (illustrative) A comms team notices a broken link-checking script on a simple newsroom archive site. Instead of diverting a developer, a team member opens a GitHub issue describing the bug and desired behavior, assigns the issue to Jules, and waits. Jules posts a readable step-by-step plan, which the reviewer can edit or reject. If approved, Jules executes the changes, runs the tests, and opens a pull request that looks like any human-contributed PR for the reviewer to merge or request further edits.

Jules runs asynchronously in the background on a single task and returns a finished pull request. That contrasts with tools that require a manager-style interface where a person orchestrates and observes multiple agents in closer to real time. Jules' readable plan-before-execution is the mechanism that lets non-developers assign work with confidence: they can redirect the agent before code is written.

# Pricing and capacity (as reported) Jules runs on Gemini models and provides tiered daily task limits via its product site: a free tier, a Pro plan, and an Ultra plan with 15, 100, and 300 tasks per day respectively. During its beta period, developers using Jules generated more than 140,000 publicly shared code improvements, according to an independent review of the platform.

# When to use Jules and when to avoid it

# Bottom line Jules can reduce the need to pull developers off other projects for routine internal-tool work. Its integration with GitHub issue and PR workflows and the pre-execution plan it produces make it suitable for comms teams that already maintain lightweight repositories and have a standard code-review process.

More context around this story.

Loading more related stories...

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app