Extract the AI provider/endpoints settings and the MCP server section out
of the Workspace "General" settings page into their own "AI" settings page,
reachable from a new sidebar entry.
- add page apps/client/.../settings/workspace/ai-settings.tsx (AiProviderSettings
admin-gated + McpSettings), with its own Helmet title
- register the /settings/ai route in App.tsx and add SETTINGS.WORKSPACE.AI
to app-route.ts
- add an "AI" item (IconSparkles) to the Workspace group in settings-sidebar
- trim workspace-settings.tsx back to the General section and drop the
now-unused imports
Add docs/mobile-app-plan.md capturing the mobile-app research: current
stack, existing responsive web inventory, why the editor must stay in a
WebView, comparison of native/Capacitor/hybrid paths, the recommended
Capacitor route, required backend changes (token-in-body login, CORS
whitelist, APNs/FCM push, optional Swagger), Android/iOS specifics, and
the offline outlook (referencing docs/offline-sync-plan.md).
Enrich the "Mobile app" roadmap entry in README.md and README.ru.md to
point to the new plan and correct the inaccurate "native" wording
(Capacitor wrapper of the existing web UI, iOS first, Android to follow).
Add docs/voice-dictation-plan.md — a ready-to-implement design covering
server-side Whisper transcription via the existing per-workspace AI provider,
with the mic button in both the AI agent chat and the page editor. The doc
consolidates four parts: STT provider credentials (full parity with the LLM
and embedding creds, incl. the encrypted stt_api_key_enc column and both
provider-field whitelists), the getTranscriptionModel builder + /transcribe
endpoint, the ai.dictation visibility toggle, and the client capture
(useDictation + MicButton). Includes edge cases, security notes, an
implementation order, and the full list of affected files.
Document migrating an existing Docmost instance to Gitmost. The DB schema
is a strict superset (additive-only migrations that auto-apply on boot), so
the move is essentially two image swaps; the only hard requirement is the
pgvector DB image for the page_embeddings RAG table (CREATE EXTENSION vector).
- Primary path: clean in-place swap from a Docmost on postgres:18
(app -> ghcr.io/vvzvlad/gitmost, db -> pgvector/pgvector:pg18), no
dump/restore, volume reused as-is.
- Notes: pg_dump backup first, identical PGDATA layout, matching the
Postgres major (pg16 case), managed-Postgres caveat, AI opt-in.
- Added to both README.md and README.ru.md.
The built-in AI agent chat over wiki content is fully implemented
(server module, ~40 tools, RAG search, provider settings, external MCP),
so showcase it in both READMEs:
- list AI agent chat among the from-scratch community replacements
- add a "What's different" table row and a dedicated feature section
- move AI chat from the "In progress" roadmap bucket to "Done"
- add it to the Features list
- add docs/screenshots/ai-chat.png and show it in the Screenshots section
Updated in sync in README.md and README.ru.md.
Rewrite README around the community fork story:
- state Gitmost is an AGPL-only fork of Docmost with NO Enterprise-Edition
code (ee dirs removed) and replacements written from scratch
- add a "What's different from Docmost" table (EE removal, comment
resolution, embedded MCP, rebranding, compact tree, GHCR CI)
- reframe the MCP section: it is our own docmost-mcp built in, better than
Docmost's coarse EE MCP (agent-native tools), and the same server as the
standalone one — just bundled (Docmost + docmost-mcp in one package)
- group the roadmap into Done / In progress / Planned; done: MCP, macOS
app; in progress: AI chat, git sync; planned: templates, viewer
comments, password-protected pages, Windows/Linux app, mobile app,
offline/PWA, and a batch of editor & UX improvements
- update the License section to reflect the absence of EE directories
- add README.ru.md (full Russian translation) and an English/Russian
language switcher to both files
