Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Built-in Office document tools (OfficeCLI integration)

オープン
  • 何か問題がありますか？
#12,728 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go
領域
ai, backend

調査の方向性

This is a design proposal, so start by reading how the existing pieces fit: LocalAIAssistantHolder and metadata.localai_assistant, DisableMutating in pkg/mcp/localaitools, and the MCP executor functions NewToolExecutor, DiscoverMCPTools, ExecuteTool and ExecuteMCPToolCallRemote. Done means maintainers agree on the modality shape, lifecycle, and sandboxing, not that code exists yet. Do not start an implementation until that is settled in the thread.

索引モデルが issue の本文から書いたものです。

説明

enhancement

Is your feature request related to a problem?
LocalAI models and agents cannot create or edit Office documents (.docx/.xlsx/.pptx) locally. Users must manually configure an external MCP server per model or per agent.

Describe the solution
I don't know if anybody thinked about before, but my proposal is to integrate OfficeCLI (Apache 2.0, single self-contained binary, built-in MCP stdio server + HTML/PNG rendering engine) as an optional built-in tool surface, following the existing LocalAI Assistant pattern:

  1. In-process / managed MCP surface — analogous to LocalAIAssistantHolder + metadata.localai_assistant: an office modality (e.g. metadata.office_documents or a DisableOfficeTools app flag) that registers OfficeCLI's MCP tools for any model without per-model YAML.
  2. Lifecycle management — LocalAI provisions/launches the officecli stdio server itself (auto-download binary or bundled), instead of requiring users to hand-write an mcp.stdio block.
  3. Agent integration — expose the same surface to the Agent pool as a built-in action / default agent-scoped MCP server, respecting allowed_tools, excluded_tools and a read-only mode (mirroring DisableMutating in pkg/mcp/localaitools).
  4. Skill prompt injection — reuse the MCP prompt-injection path to surface OfficeCLI's SKILL.md guidance to the model when the modality is active.

Why it fits

  • The existing MCP executor (NewToolExecutor, DiscoverMCPTools, ExecuteTool) already supports stdio servers and the server-side tool loop across /v1/chat/completions, Anthropic Messages, Open Responses (stream + background).
  • OfficeCLI's MCP tool has a single command string param — trivially compatible with the generic CallTool path.
  • Distributed mode: the tool would execute on agent workers via ExecuteMCPToolCallRemote, so the binary only needs to exist on worker nodes.

Workaround today
Manually adding OfficeCLI as mcp.stdio in the model YAML or as an agent-scoped stdio server — but this requires installing the binary yourself and repeating the config per model/agent.

Security considerations

  • File-system access should be sandboxed/scoped (configurable working dir).
  • Read-only mode (view/get/query/validate only) for untrusted contexts.
  • Disabled by default, opt-in flag — same posture as the LocalAI Assistant.

Other considerations
Integrate office features is so important to a professional and enterprise use of LocalAI.

主要言語
Go
スター
49.5k
フォーク
4.5k
平均マージ
23時間 40分
マージ済み PR（30日）
381

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

mudler/LocalAI のほかの issue

mudler/LocalAI の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。