Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Built-in Office document tools (OfficeCLI integration)

Abierto
  • ¿Algo no está bien?
#12,728 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
ai, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area/tools community-integrations 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.

Lenguaje dominante
Go
Estrellas
49.8k
Forks
4.5k
Merge medio
18 h 28 min
PR fusionados (30 d)
347

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de mudler/LocalAI

Todos los issues de mudler/LocalAI

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.