PatentForge v0.5.0 — merged-product release, cloud or local #18
scottconverse
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
PatentForge v0.5.0 is the first release of the merged product. PatentForgeLocal (the local-only fork) and the original PatentForge (the cloud-only product) are now one application called PatentForge. Pick Local mode (Ollama + Gemma 4 on your hardware) or Cloud mode (Anthropic Claude via your own API key). Switch any time in Settings.
This release closes an 8-run merge plan that took the two prior products and stitched them together behind a single LLM provider abstraction.
What's new
$N.NNNin Cloud mode.What's the same
Migration from PatentForgeLocal
If you have PatentForgeLocal v0.1.x installed: install the new Full edition over it.
patentforgelocal.dbis silently renamed topatentforge.dbon first boot. Your projects carry over.Migration from the original PatentForge cloud-only product
If you have the original
scottconverse/patentforgeclone: that repo is being archived. The merged product replaces it.Behind the scenes (the 8-run merge plan)
For the curious — here's how we got here. Each run shipped behind audit + a PR.
docs/parity-audit.mdproduced.LLMClientboundary, retry pushed to LiteLLM, per-service dispatch.AppSettings.provider+ encryptedcloudApiKeycolumns; idempotent migration; SQLite CHECK constraint enforcing'LOCAL' | 'CLOUD'.[Unreleased]→[0.5.0], service-side branding cleanup tail, release.Verification
841 automated tests green across all subprojects:
Cleanroom end-to-end verification (full live stack with real Ollama + Anthropic API) is an operator pre-cutover step, not part of the autonomous test suite.
Known follow-ups
These are tracked as focused sub-issues post-v0.5.0:
feasibilityservice Cloud branch — currently throwsLLMClientCloudNotImplementedErrorpending the Anthropic streaming + tool-call adapter. The 3 Python services already work in both modes via LiteLLM; running feasibility in Cloud mode is queued.ollamaWebSearchApiKeycolumn restore — Run 4 droppedollamaApiKeyon a misreading of the field's purpose. Frontend retains the input field; backend column needs to be restored under a clearer name.ClaimsTab.tsx:428ClaimData/ClaimNode mismatch + 4×useViewInit.test.tsInventionInput fixture rows missing projectId. Baseline carried since pre-merge.<button>rather than<input type="radio">— slight a11y polish surfaced in Run 6 audit Lens 2.patentforgelocal-tray.exe→patentforge-tray.exe, etc.) — coordinated with the build pipeline; post-release follow-up.github.com/scottconverse/patentforgelocal/*→.../patentforge/*) — coordinated with the GitHub repo rename.scottconverse/patentforgelocal→scottconverse/patentforge) and archive of the upstreamscottconverse/patentforgecloud-only repo — operator-driven destructive actions executed post-merge.Where to download
GitHub Releases — pick the Lean or Full edition for your platform:
PatentForge-{Lean,Full}-0.5.0-Setup.exePatentForge-{Lean,Full}-0.5.0.dmgPatentForge-{Lean,Full}-0.5.0.AppImage(Release artifacts produced by the per-platform installer build scripts post-merge.)
Credits
PatentForge stands on excellent open-source work:
Legal note
PatentForge is a research tool, not a legal service. The author is not a lawyer. The AI is not a lawyer. AI-generated analysis may contain errors, omissions, or fabricated references. Always consult a registered patent attorney before making filing, licensing, or enforcement decisions.
See
LEGAL_NOTICE.mdfor the full disclaimer.Have questions? Open an issue, or post in this Discussions thread.
All reactions