{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-hirokimukai-jules-extension","slug":"jules-extension","name":"Jules Extension","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=HirokiMukai.jules-extension","page_url":"https://unfragile.ai/jules-extension","categories":["code-editors"],"tags":["ai","ai-agent","artificial-intelligence","automation","code-agent","coding-agent","coding-assistant","development-tools","gemini","google","jules","LLM","productivity","vscode-extension"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-hirokimukai-jules-extension__cap_0","uri":"capability://tool.use.integration.api.driven.jules.ai.agent.task.assignment.with.vscode.command.palette.integration","name":"api-driven jules ai agent task assignment with vscode command palette integration","description":"Enables developers to create new coding tasks and assign them to Google's Jules AI agent directly from VSCode's command palette without leaving the editor. The extension acts as a thin client that sends task descriptions via the Jules API, establishing a new session that persists in the sidebar for monitoring. Task creation is initiated through the `Jules: Create Jules Session` command, which opens a dialog for task input and routes the request to the Jules backend API using the stored API key from VSCode's SecretStorage.","intents":["I want to assign a coding task to an AI agent without switching applications","I need to create a new Jules session with a specific task description from my editor","I want to quickly delegate code generation work while staying in my development environment"],"best_for":["Solo developers using VSCode who want to delegate coding tasks to AI agents","Teams using Jules as their primary AI coding agent and VSCode as their editor"],"limitations":["Task descriptions are text-only; no ability to pre-select files or code snippets for context in the command palette UI","No built-in task templates or quick-start prompts — developers must manually type task descriptions each time","API key must be set up before any task creation is possible; no graceful fallback or inline setup during task creation"],"requires":["VSCode installed (minimum version unknown)","Valid Google Jules API key obtained from Jules platform","Active internet connection to Jules API endpoint"],"input_types":["text (task description)"],"output_types":["session object (stored in sidebar view with status)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_1","uri":"capability://memory.knowledge.real.time.jules.session.status.monitoring.and.activity.log.visualization.in.sidebar","name":"real-time jules session status monitoring and activity log visualization in sidebar","description":"Displays active Jules coding sessions in a dedicated VSCode sidebar view (`julesSessionsView`) that shows real-time session status (Running, Active, Done, etc.) and provides access to detailed activity logs. The sidebar acts as a persistent window into the Jules agent's execution, showing command history, file modifications, and reasoning steps without requiring developers to switch to the Jules web application. Status updates are retrieved via polling or API callbacks (mechanism unknown), and activity logs are fetched on-demand when a session is selected.","intents":["I want to monitor the progress of my Jules AI agent without switching to the web dashboard","I need to see what commands Jules executed and what files it modified","I want to review the AI agent's reasoning and decision-making process in real-time"],"best_for":["Developers who want to keep Jules session monitoring within their primary development environment","Teams that need transparency into AI agent actions for code review and audit purposes"],"limitations":["Status updates appear to require manual refresh or polling; no real-time push notifications documented","Activity logs are read-only; developers cannot interrupt or pause running commands from the sidebar (only send follow-up messages)","No filtering, search, or sorting of activity logs — all entries displayed in chronological order only","Sidebar view is VSCode-only; no mobile or remote monitoring capability"],"requires":["VSCode installed","At least one active Jules session created via the extension","Active internet connection to fetch session status and activity logs"],"input_types":["session ID (internal)"],"output_types":["structured session status (Running/Active/Done/etc.)","activity log entries (text with timestamps)","execution history (command names, file paths, results)"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_2","uri":"capability://code.generation.editing.code.diff.visualization.and.review.for.jules.generated.changes","name":"code diff visualization and review for jules-generated changes","description":"Provides an integrated diff viewer within VSCode that displays code changes generated by the Jules AI agent before or after execution. The extension fetches the latest code modifications from the Jules API and renders them using VSCode's native diff editor, allowing developers to review additions, deletions, and modifications side-by-side. This capability enables code review workflows where developers can inspect what Jules changed without manually comparing file versions or switching to Git diff tools.","intents":["I want to review the code changes Jules generated before they are committed","I need to see exactly what lines were added, removed, or modified by the AI agent","I want to compare Jules's changes against the original code without leaving VSCode"],"best_for":["Developers who want to review AI-generated code changes before merging or committing","Teams implementing code review workflows with AI agents where human approval is required"],"limitations":["Diff viewer is read-only; no inline editing or commenting on diffs from the extension","No multi-file diff summary or change statistics (e.g., lines added/removed per file)","Diffs are fetched from Jules API; no local diff computation or caching documented","No integration with Git diff tools or version control systems for historical comparison"],"requires":["VSCode installed","Active Jules session with completed code generation","Active internet connection to fetch diff data from Jules API"],"input_types":["session ID (internal)"],"output_types":["unified diff format (rendered in VSCode diff editor)","file paths and line numbers for changes"],"categories":["code-generation-editing","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_3","uri":"capability://planning.reasoning.execution.plan.generation.and.approval.workflow.before.jules.runs.commands","name":"execution plan generation and approval workflow before jules runs commands","description":"Jules generates a detailed execution plan for the assigned task, which the extension displays to the developer for review and approval before any code changes or commands are executed. The developer can inspect the plan (contents and format unknown) and either approve it via the `Jules: Approve Plan` command or send follow-up messages to refine the plan. This creates a human-in-the-loop checkpoint where developers retain control over what the AI agent will do before it modifies files or runs commands.","intents":["I want to review Jules's plan before it executes any code changes","I need to approve or reject the AI agent's approach to my task","I want to send feedback to Jules to refine its plan before execution"],"best_for":["Teams that require human approval before AI agents modify code","Developers who want to maintain control over AI agent behavior and prevent unintended changes","Organizations with compliance or code review requirements"],"limitations":["Plan format and level of detail are unknown; no documentation on what information is included","No ability to edit or modify the plan directly; only approve/reject or send messages for refinement","Plan approval is blocking; Jules cannot proceed until developer explicitly approves","No timeout or auto-approval mechanism documented; developer must manually approve each plan"],"requires":["VSCode installed","Active Jules session with a generated execution plan","Developer availability to review and approve plans in a timely manner"],"input_types":["execution plan (from Jules API)","approval decision (approve/reject)","follow-up messages (text)"],"output_types":["approval status (approved/rejected)","plan execution trigger (if approved)"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_4","uri":"capability://text.generation.language.iterative.task.refinement.through.follow.up.messages.to.active.jules.sessions","name":"iterative task refinement through follow-up messages to active jules sessions","description":"Allows developers to send follow-up messages to an active Jules session to provide feedback, course-correct the AI agent, or request modifications to the task approach. The extension routes these messages through the Jules API to the active session, enabling a conversational workflow where developers can guide the agent's behavior without creating a new session. This capability supports iterative development where the initial task may need refinement based on intermediate results or changing requirements.","intents":["I want to send feedback to Jules mid-execution to adjust its approach","I need to ask Jules to modify the task or try a different approach without starting over","I want to have a conversation with the AI agent to refine the solution iteratively"],"best_for":["Developers working on complex tasks that may require iterative refinement","Teams using Jules for exploratory coding where the final approach is not known upfront","Developers who prefer conversational interaction with AI agents over one-shot task assignment"],"limitations":["Message-based feedback only; no ability to directly edit code or provide code snippets in follow-up messages (unclear from documentation)","No conversation history or transcript displayed in the extension (activity logs show execution history, not message history)","Follow-up messages are asynchronous; no real-time chat interface or immediate response from Jules","No ability to interrupt or pause Jules execution before sending follow-up messages; only message-based feedback"],"requires":["VSCode installed","Active Jules session (not completed or done)","Active internet connection to Jules API"],"input_types":["text message (follow-up instruction or feedback)"],"output_types":["message acknowledgment (status)","updated execution plan or results (from Jules)"],"categories":["text-generation-language","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_5","uri":"capability://safety.moderation.secure.api.key.management.with.vscode.secretstorage.integration","name":"secure api key management with vscode secretstorage integration","description":"Manages Jules API key storage securely using VSCode's built-in SecretStorage API, which encrypts credentials at rest and prevents plaintext exposure in configuration files or logs. The extension provides commands to set (`Jules: Set Jules API Key`), verify (`Jules: Verify API Key`), and manage API keys without exposing them in VSCode settings or terminal output. This approach leverages VSCode's native credential management rather than storing keys in plaintext configuration files or environment variables.","intents":["I want to securely store my Jules API key in VSCode without exposing it in plaintext","I need to verify that my API key is valid before using the extension","I want to update or rotate my Jules API key without manually editing configuration files"],"best_for":["Individual developers using VSCode who want secure credential management","Teams where VSCode is the standard editor and credential security is a requirement"],"limitations":["API key is stored per VSCode installation; switching machines or VSCode profiles requires re-entering the key","No key rotation or expiration management built into the extension","SecretStorage is VSCode-specific; API key cannot be shared across other tools or IDEs","No audit logging of API key access or usage; only storage is secured"],"requires":["VSCode installed (SecretStorage API available in recent versions)","Valid Google Jules API key from Jules platform"],"input_types":["API key (text string)"],"output_types":["verification status (valid/invalid)","stored credential (encrypted in SecretStorage)"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_6","uri":"capability://tool.use.integration.github.integration.for.pull.request.status.checks.and.pr.creation","name":"github integration for pull request status checks and pr creation","description":"Optionally integrates with GitHub to enable Jules to check pull request status and create or update PRs based on code changes. Developers can authenticate with GitHub via the `Jules: Sign in to GitHub` command, allowing Jules to interact with GitHub repositories without requiring manual PR creation. The extension can open created PRs in the browser for review and merging. This capability bridges Jules's code generation with GitHub's collaboration and review workflows.","intents":["I want Jules to create a pull request automatically after generating code changes","I need to check PR status from Jules sessions without switching to GitHub","I want to open Jules-created PRs in GitHub for team review and merging"],"best_for":["Teams using GitHub for version control and code review","Developers who want to automate PR creation as part of Jules task execution","Organizations where AI-generated code must go through GitHub PR review workflows"],"limitations":["GitHub integration is optional; not required for core Jules functionality","No documentation on PR creation workflow, templates, or customization options","PR status checks are read-only; no ability to approve, merge, or comment on PRs from the extension","GitHub authentication is separate from Jules API key; requires additional setup and sign-in","No support for GitHub Enterprise or self-hosted GitHub instances (unclear from documentation)"],"requires":["VSCode installed","GitHub account with access to target repositories","GitHub authentication token (obtained via `Jules: Sign in to GitHub` command)","Jules session with code changes to create PR from"],"input_types":["GitHub authentication (OAuth token)","PR metadata (title, description, branch name — format unknown)"],"output_types":["PR URL (for opening in browser)","PR status (created/updated/failed)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_7","uri":"capability://memory.knowledge.local.session.cache.management.with.selective.deletion","name":"local session cache management with selective deletion","description":"Maintains a local cache of Jules sessions in VSCode, allowing developers to clear the entire cache or delete individual sessions via the `Jules: Clear Cache` and `Jules: Delete Session from Local Cache` commands. This capability enables offline access to session history and reduces API calls for frequently accessed sessions. The cache is stored locally on the developer's machine and persists across VSCode restarts, but can be manually cleared if storage space is needed or sessions need to be archived.","intents":["I want to clear old Jules sessions from my VSCode sidebar to reduce clutter","I need to delete a specific session without affecting other sessions","I want to free up local storage by clearing the session cache"],"best_for":["Developers who run many Jules sessions and want to manage local storage","Teams that need to archive or delete sensitive session data from local machines"],"limitations":["Cache management is local-only; deleting from cache does not affect Jules server-side session history","No selective cache retention policies (e.g., keep last N sessions); only manual deletion or full clear","No cache size limits or automatic cleanup; developers must manually manage cache growth","Deleted sessions cannot be recovered from local cache; no undo or recovery mechanism","No documentation on cache storage location or format"],"requires":["VSCode installed","At least one Jules session in the local cache"],"input_types":["session ID (for selective deletion) or clear-all flag"],"output_types":["cache status (cleared/deleted)","confirmation message"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_8","uri":"capability://tool.use.integration.vscode.settings.panel.for.extension.configuration","name":"vscode settings panel for extension configuration","description":"Provides a dedicated settings panel accessible via the `Jules: Open Settings` command, allowing developers to configure extension behavior and preferences. The specific configuration options available are not documented, but the settings panel likely includes options for API endpoint configuration, session display preferences, notification settings, and other extension-level customizations. This capability centralizes extension configuration in VSCode's standard settings UI rather than requiring manual configuration file editing.","intents":["I want to configure Jules extension settings without editing JSON configuration files","I need to customize how Jules sessions are displayed and monitored in VSCode","I want to adjust extension behavior (e.g., notifications, auto-refresh) to match my workflow"],"best_for":["Developers who prefer VSCode's GUI settings panel over manual configuration","Teams with standardized extension configuration requirements"],"limitations":["Specific configuration options are not documented; unclear what settings are available","No documentation on default values or recommended settings","Settings are local to VSCode installation; no team-wide configuration sharing or synchronization","No validation or preview of settings changes before applying"],"requires":["VSCode installed","Jules extension installed"],"input_types":["configuration key-value pairs (format unknown)"],"output_types":["updated extension configuration (persisted in VSCode settings)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-hirokimukai-jules-extension__cap_9","uri":"capability://tool.use.integration.web.bridge.for.opening.jules.sessions.in.external.web.application","name":"web bridge for opening jules sessions in external web application","description":"Provides the ability to open active Jules sessions in the external Jules web application directly from VSCode, allowing developers to access the full-featured web dashboard when needed. This capability acts as a bridge between the VSCode extension (which provides lightweight session monitoring and task creation) and the Jules web application (which likely offers advanced features like detailed analytics, team collaboration, and complex session management). Developers can toggle between the VSCode extension and web dashboard without losing session context.","intents":["I want to access the full Jules web dashboard for advanced features not available in VSCode","I need to share a Jules session with team members via the web application","I want to view detailed analytics or reports on Jules sessions"],"best_for":["Developers who use both VSCode and the Jules web dashboard","Teams that need advanced Jules features available only in the web application","Organizations where session sharing and collaboration require the web interface"],"limitations":["Web bridge is one-way; changes made in the web dashboard may not immediately sync back to VSCode","No documentation on which features are VSCode-only vs. web-only","Opening the web application requires switching context away from VSCode","No embedded web view within VSCode; must use external browser"],"requires":["VSCode installed","Active Jules session","Web browser with access to Jules web application","Active internet connection"],"input_types":["session ID (internal)"],"output_types":["web application URL (opened in browser)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":38,"verified":false,"data_access_risk":"high","permissions":["VSCode installed (minimum version unknown)","Valid Google Jules API key obtained from Jules platform","Active internet connection to Jules API endpoint","VSCode installed","At least one active Jules session created via the extension","Active internet connection to fetch session status and activity logs","Active Jules session with completed code generation","Active internet connection to fetch diff data from Jules API","Active Jules session with a generated execution plan","Developer availability to review and approve plans in a timely manner"],"failure_modes":["Task descriptions are text-only; no ability to pre-select files or code snippets for context in the command palette UI","No built-in task templates or quick-start prompts — developers must manually type task descriptions each time","API key must be set up before any task creation is possible; no graceful fallback or inline setup during task creation","Status updates appear to require manual refresh or polling; no real-time push notifications documented","Activity logs are read-only; developers cannot interrupt or pause running commands from the sidebar (only send follow-up messages)","No filtering, search, or sorting of activity logs — all entries displayed in chronological order only","Sidebar view is VSCode-only; no mobile or remote monitoring capability","Diff viewer is read-only; no inline editing or commenting on diffs from the extension","No multi-file diff summary or change statistics (e.g., lines added/removed per file)","Diffs are fetched from Jules API; no local diff computation or caching documented","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.33,"quality":0.3,"ecosystem":0.35000000000000003,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.803Z","last_scraped_at":"2026-05-03T15:20:31.090Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=jules-extension","compare_url":"https://unfragile.ai/compare?artifact=jules-extension"}},"signature":"iWh4hgcjSToa41KU5I1jFhtbYl12XD4N6NYuOQ9/r2YI6EHdWjpEx09/ATM0MkB5AxLpNifz6Wv7P/hOvAKrDw==","signedAt":"2026-06-16T22:49:55.123Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/jules-extension","artifact":"https://unfragile.ai/jules-extension","verify":"https://unfragile.ai/api/v1/verify?slug=jules-extension","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}