Skip to content

feat: document llmman as a local AI server alternative to Ollama - #8990

Open
ericcurtin wants to merge 1 commit into
AppFlowy-IO:mainfrom
ericcurtin:llmman
Open

ericcurtin wants to merge 1 commit into
AppFlowy-IO:mainfrom
ericcurtin:llmman

Conversation

@ericcurtin

@ericcurtin ericcurtin commented Sep 4, 2026

Copy link
Copy Markdown

Adds llmman, a local model runner that serves the Ollama API on port 17434, as a documented alternative to Ollama for Local AI.

  • ollama_setting_bloc.dart: add kDefaultOllamaServerUrl / kDefaultLlmmanServerUrl and show both in the server-url hint. The existing OllamaSettingBloc and Rust LocalAIController are reused unchanged, so there is no second provider code path.
  • controller.rs: doc comment on LocalAISetting.ollama_server_url noting any Ollama-API server works.
  • en-US.json: mention llmman alongside Ollama in aiSettingsDescription (source locale only; others are managed via Fink).

Testing: rustfmt --check (repo rustfmt.toml) on controller.rs clean; en-US.json parses; dart format leaves the edited lines unchanged. Not run: flutter analyze/flutter test (no pinned Flutter SDK locally).


PR Checklist

  • My code adheres to AppFlowy's Conventions
  • I've listed at least one issue that this PR fixes in the description above. (No existing issue.)
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing. (Not run locally; see Testing.)

AI-assisted, reviewed before submitting.

Summary by Sourcery

Support llmman as an alternative Ollama-compatible local AI server.

New Features:

  • Document llmman as a supported local AI server option alongside Ollama.

Enhancements:

  • Clarify that the local AI configuration accepts any server implementing the Ollama API.

Documentation:

  • Update the English AI settings description to mention llmman alongside Ollama.

@sourcery-ai

sourcery-ai Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This documentation-focused PR exposes llmman as a selectable Ollama-compatible server through the existing Local AI configuration, adds an explicit warning about its missing embedding endpoint, and updates user-facing provider text without introducing a second implementation.

File-Level Changes

Change Details Files
Makes llmman discoverable as an Ollama-compatible local AI server without adding a new provider or code path.
  • Adds named default URLs for Ollama and llmman and displays both in the existing server URL hint.
  • Documents that the existing Ollama setting and Rust controller accept any Ollama-API-compatible server, while llmman lacks embedding support.
  • Updates the source English AI settings description to mention llmman.
  • Keeps the existing Ollama UI, controller, and embedding implementation unchanged.
frontend/appflowy_flutter/lib/workspace/application/settings/ai/ollama_setting_bloc.dart
frontend/rust-lib/flowy-ai/src/local_ai/controller.rs
frontend/resources/translations/en-US.json
Validates the documentation-oriented changes with targeted formatting and syntax checks while recording environment limitations.
  • Confirms Rust formatting and JSON validity.
  • Confirms Dart formatting stability for the edited lines.
  • Notes that the existing cargo check failure is unrelated and that Flutter analysis/tests and live server compatibility were not verified.
frontend/rust-lib/flowy-ai/src/local_ai/controller.rs
frontend/appflowy_flutter/lib/workspace/application/settings/ai/ollama_setting_bloc.dart
frontend/resources/translations/en-US.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="frontend/appflowy_flutter/lib/workspace/application/settings/ai/ollama_setting_bloc.dart" line_range="236" />
<code_context>
           content: serverUrl,
-          hintText: 'http://localhost:11434',
+          hintText:
+              '$kDefaultOllamaServerUrl (Ollama) or $kDefaultLlmmanServerUrl (llmman)',
           settingType: SettingType.serverUrl,
         ),
</code_context>
<issue_to_address>
**issue (broader_impact):** Pointing the setting at llmman does not provide a usable chat-only configuration: `update_local_ai_setting` validates both the chat and embedding models through `/api/tags`, and the embedding scheduler continues to call Ollama `/api/embed`. A llmman setup without the required embedding model is rejected when the URL is saved, while a setup that passes model validation fails when indexing or search invokes embeddings, so the UI hint and documentation present llmman as a drop-in without explaining that the existing Local AI path can block or fail the entire configuration.

**Triggers:** When a user configures llmman with its supported chat models and attempts to save the setting or use local AI search/indexing.

**Suggested fix:** Either allow a chat-only llmman configuration without requiring the embedding model, or explicitly state in the UI that llmman cannot currently be used for AppFlowy Local AI until the embedding path is implemented.

```suggestion
              '$kDefaultOllamaServerUrl (Ollama); llmman cannot currently be used for AppFlowy Local AI until the embedding path is implemented',
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

content: serverUrl,
hintText: 'http://localhost:11434',
hintText:
'$kDefaultOllamaServerUrl (Ollama) or $kDefaultLlmmanServerUrl (llmman)',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (broader_impact): Pointing the setting at llmman does not provide a usable chat-only configuration: update_local_ai_setting validates both the chat and embedding models through /api/tags, and the embedding scheduler continues to call Ollama /api/embed. A llmman setup without the required embedding model is rejected when the URL is saved, while a setup that passes model validation fails when indexing or search invokes embeddings, so the UI hint and documentation present llmman as a drop-in without explaining that the existing Local AI path can block or fail the entire configuration.

Triggers: When a user configures llmman with its supported chat models and attempts to save the setting or use local AI search/indexing.

Suggested fix: Either allow a chat-only llmman configuration without requiring the embedding model, or explicitly state in the UI that llmman cannot currently be used for AppFlowy Local AI until the embedding path is implemented.

Suggested change
'$kDefaultOllamaServerUrl (Ollama) or $kDefaultLlmmanServerUrl (llmman)',
'$kDefaultOllamaServerUrl (Ollama); llmman cannot currently be used for AppFlowy Local AI until the embedding path is implemented',

llmman (https://github.com/llmmanorg/llmman) serves the Ollama API on
port 17434, so Local AI already works against it by changing the server
url, but nothing in the app made that discoverable.

- Add kDefaultOllamaServerUrl / kDefaultLlmmanServerUrl and show both
  in the server url hint.
- Note on LocalAISetting.ollama_server_url that any Ollama-API server
  works; mention llmman next to Ollama in the en-US settings text.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants