0.11.0

Added

• Browser/MCP: add non-destructive ChatGPT Project Sources management (oracle project-sources list|add, MCP project_sources) so Developer Mode workflows can share explicit project context through Sources. Addresses #131 and builds on #132 by @vgorlovi.
• Browser: add repeatable --browser-follow-up prompts and MCP browserFollowUps for multi-turn ChatGPT browser consults in one conversation. (#170) — thanks @pdurlej.
• Browser: add live ChatGPT tab inspection, oracle status --browser-tabs, browser session harvest/live-tail commands, and --browser-tab <ref> to reuse an existing ChatGPT tab by current tab, target id, URL, or title substring. (#126) — thanks @NathanSkene.
• Browser: add --browser-research deep / MCP browserResearchMode: "deep" for ChatGPT Deep Research browser runs, including progress monitoring, reattach recovery, and iframe report capture. (#151) — thanks @pdurlej.
• Browser: save durable browser session artifacts, including transcripts, Deep Research reports, and ChatGPT-generated image files when downloadable image URLs are present. (#169) — thanks @pdurlej.
• Browser: add --browser-archive / MCP browserArchive to archive successful one-shot ChatGPT browser runs after local artifacts are saved. (#178) — thanks @pdurlej.
• Browser: add --browser-attach-running to reuse a local already-running signed-in Chrome through Chrome's local remote-debugging toggle. Oracle opens a dedicated tab, stores attach metadata for reattach, and leaves the browser itself untouched. (#119) — thanks @dedene.
• MCP: add the chatgpt-pro-heavy consult preset, MCP dry-runs, browser model strategy passthrough, and oracle bridge claude-config --local-browser for Claude Code + local ChatGPT Pro browser consults. (#149) — thanks @pdurlej.
• Browser: coordinate concurrent ChatGPT browser runs that share one manual-login profile with a tab lease registry, --browser-max-concurrent-tabs, stale lease cleanup, and shared Chrome discovery. (#150) — thanks @pdurlej.
• Browser: print a browser control plan before ChatGPT runs and dry-runs, and clean up leftover blank tabs after completed manual-profile runs. (#179) — thanks @pdurlej.
• Browser: document multi-turn consult guardrails and make browser dry-runs explicit that Oracle only sends caller-provided follow-up prompts. (#180) — thanks @pdurlej.

Docs

• Browser: document the new attach-running workflow and add a manual smoke test for the direct attach path.
• Website: add the generated askoracle.dev docs site, social preview asset, and GitHub Pages deployment workflow.

Changed

• Browser: emit --heartbeat status while waiting for ChatGPT browser responses, including safe Thinking/Reasoning sidecar liveness metadata without logging reasoning text. (#148) — thanks @pdurlej.

Fixed

• Browser/MCP: harden ChatGPT Pro browser consults with louder GPT-5.5 Pro selection validation, resolved MCP dry-run details, assistant-timeout diagnostics, incomplete-capture reattach metadata, and clean Pro Extended live-run metadata. (#177) — thanks @pdurlej.
• Browser: clear stale ChatGPT composer drafts before initial browser submissions and ignore model-picker thinking-effort controls while scanning model rows. (#176) — thanks @oirehT.
• Browser: keep the completed conversation tab open when --browser-keep-browser is set so oracle status --browser-tabs, harvest, and --browser-tab current can inspect/reuse it.
• Browser: retry Chrome remote-debugging approval 403 responses for --browser-attach-running and report the actionable approval/toggle guidance instead of a raw websocket error.
• Browser: fail fast when ChatGPT shows an account security block during Deep Research, instead of waiting until the research timeout.
• Browser: strengthen live upload verification so smoke tests catch cases where ChatGPT accepts a file chip but cannot read the uploaded content.
• Bridge: keep generated Codex/Claude MCP config snippets clean on stdout so redirecting oracle bridge claude-config --local-browser > .mcp.json produces valid JSON.
• MCP: clarify consult engine defaults and add ChatGPT browser-mode recovery guidance to missing GPT API-key errors. (#172) — thanks @pdurlej.