You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,15 @@ Neo Chat is a self-hostable, local-first AI chat application built with Next.js,
24
24
25
25
It is designed for people who want the power of modern AI workspaces without giving up local data ownership. Chat history, workspace metadata, skills, plugin configuration, memories, and files stay in the browser by default; server routes act as controlled proxies for model providers, search, RAG, document parsing, voice, plugin execution, and deployment health.
26
26
27
+
## v2.1.0 Highlights
28
+
29
+
- Rebuilt System Settings with clearer grouped controls, an About panel, deployment health visibility, and local data export/reset actions.
30
+
- Added native model image generation/editing with ordered mixed text/image output blocks and OPFS-backed image display caching.
31
+
- Added thinking intensity controls for reasoning-capable Gemini and OpenAI-compatible models.
32
+
- Added Japanese localization for the app shell, SEO metadata, assistant locale routing, voice language handling, and the public Skills catalog.
33
+
- Hardened hosted deployments with API request proof, shared-store checks, service health coverage, safer URL/secret handling, and Cloudflare Worker command fixes.
34
+
- Added changelog-driven GitHub Release automation and a fork-only upstream sync workflow.
35
+
27
36
## Features
28
37
29
38
- Multi-provider chat with Gemini, OpenAI, and OpenAI-compatible endpoints.
@@ -409,6 +418,25 @@ Project documentation:
409
418
-[Roadmap](ROADMAP.md)
410
419
-[Changelog](CHANGELOG.md)
411
420
421
+
### Fork Synchronization
422
+
423
+
Fork maintainers can enable the `Sync upstream` workflow to fast-forward their fork from the upstream `u14app/neo-chat``main` branch.
424
+
425
+
1. In the fork, open **Settings > Actions > General** and allow GitHub Actions to run.
426
+
2. In **Workflow permissions**, select **Read and write permissions** so `GITHUB_TOKEN` can push to the fork.
427
+
3. Open **Actions > Sync upstream > Run workflow** to trigger the first sync manually.
428
+
4. Keep the scheduled workflow enabled if you want the fork to sync daily.
429
+
430
+
The workflow is skipped in the upstream repository and only runs when GitHub marks the repository as a fork. It uses fast-forward-only merging, so it fails safely when the fork branch has diverged from upstream or a branch protection rule blocks the push.
431
+
432
+
Optional repository variables can override the defaults:
0 commit comments