Jules Workspace
What do you want to build, fix, investigate, or improve?
Describe the work once. Jules resolves context and keeps the draft ready for the next step.
From one instruction to reviewed code
PlatPhorm Jules turns a plain-language request into a traceable coding session without making you assemble provider payloads. Choose one of the available platphorm-* repositories, confirm the branch and completion behavior, then follow the plan, activity, evidence, and pull request from one session page. Historical and active provider runs are reconciled into Cloudflare D1, so the work queue remains responsive without polling Google from the browser.
Repository and branch controls come from server-side GitHub and Google Jules sources, sorted for quick selection. Sessions that require review pause at plan approval; sessions awaiting clarification accept follow-up feedback in place.
Google Jules API referenceSchedules live in D1 and are evaluated by a named Cloudflare Worker. Operators can create, edit, pause, enable, or run them immediately, while public readers see bounded status without protected instructions.
Manage schedulesJules exposes a PR control only when the provider returned a real GitHub URL for an in-scope repository. Approval and squash merge use server-side credentials, reject drafts and conflicts, and pin the merge to the reviewed head SHA.
GitHub pull request APIPublished by PlatPhormNews. Product surfaces last reviewed . See the AI policy, privacy boundary, and machine-readable trust policy.
No Jules sessions yet
Create a local implementation draft or use the protected APIs for configured provider workflows.
Checking backend persistence state.