web-app-ai-doc-summary is the first AI extension to ship into the ownCloud web-extensions repository since we relicensed it to Apache-2.0 on June 15th. Lukas Hirt wrote it in a week.<\/p>\n
Open a PDF, TXT, or Markdown file in oCIS. A Summary tab appears in the sidebar. Click it. You get a 2\u20133 sentence overview and 3\u20134 key points, generated by whichever LLM you’ve configured. The summary appears in your preferred interface language \u2014 the extension detects it via BCP 47 and tells the model to respond accordingly.<\/p>\n
That last detail is not a footnote. It’s the feature. A Bavarian school teacher opens a PDF report in German. The summary is in German. A Dutch researcher opens an English-language paper. The summary is in Dutch. No configuration required. The extension reads the user’s browser language preference and instructs the model automatically.<\/p>\n
There’s also a context menu action. Right-click any supported file in the file list. „Summarise.“ Same result, without opening the full file viewer first.<\/p>\n
The extension accepts an endpoint, a model name, and an optional API key via application config. The endpoint is any OpenAI-compatible API. That means OpenAI if you’re using it. It also means Ollama running on a server in your data centre. Or any of the dozens of LLM serving frameworks that implement the OpenAI API format \u2014 vLLM, LM Studio, Llama.cpp server, LocalAI.<\/p>\n
This is the architectural decision that makes the sovereign story real. Not „we chose not to build in a cloud AI dependency.“ Simply: the extension takes an endpoint. You choose what’s behind that endpoint. If it’s a self-hosted model on European infrastructure, your documents never leave European infrastructure.<\/p>\n
For developers getting started locally, Lukas wired an Ollama service directly into the dev docker-compose stack with a Traefik config. Clone the repo, run docker-compose up, and have a local LLM available for testing without any external API key or cloud account.<\/p>\n
Three PRs in three days from the same developer on the same repository:<\/p>\n
The relicensing was the precondition. The AI extensions are the payoff.<\/p>\n
Configuration is via application config, not per-user settings. An oCIS administrator configures the LLM endpoint and model once. Users get the Summary tab without any setup on their end. If you’re running a self-hosted Ollama instance, point the extension at it.<\/p>\n
github.com\/owncloud\/web-extensions<\/a><\/p>\n The Ollama dev stack is ready to use. Clone the repo, check the docker-compose config, run it, and you have a local LLM and a local oCIS instance for testing. The E2E test suite runs against this stack.<\/p>\n The AI development guide is at owncloud.dev<\/a>. The AI-Assisted Contribution Policy<\/a> is published at kiteworks.com\/opensource<\/a>.<\/p>\n Build something.<\/p>\nFor Developers<\/h3>\n
\n