gitwtfhub

wtf is octo-smart-summary?

mininglamp-oss/octo-smart-summary — explained in plain English

Analysis updated 2026-05-18

14GoAudience · developerComplexity · 2/5LicenseSetup · moderate

TL;DR

A Go microservice that uses an LLM to turn long chat threads into structured summaries with decisions, open questions, and follow ups.

Mindmap

mindmap
  root((octo-smart-summary))
    What it does
      Summarize chat threads
      Structured JSON output
      Decisions and open questions
    Tech stack
      Go service
      REST API
      Any OpenAI-compatible LLM
    Use cases
      Meeting recaps
      Feed task managers
      Streaming summaries
    Audience
      Backend developers
      OCTO ecosystem users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Automatically summarize long team chat threads into key decisions and open questions.

REASON 2

Feed structured meeting summaries into a task manager as draft to-dos.

REASON 3

Swap in any OpenAI-compatible LLM backend without changing the service code.

REASON 4

Stream summary output to a live dashboard as it is generated.

What's in the stack?

GoREST APIOpenAI-compatible LLM

How it stacks up

mininglamp-oss/octo-smart-summarygizmodata/adbc-driver-quackgokele/ovh
Stars141414
LanguageGoGoGo
Setup difficultymoderatemoderatemoderate
Complexity2/53/53/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Needs a running OpenAI-compatible LLM endpoint and API key before the service can summarize anything.

Use, modify, and distribute freely, including commercially, as long as you keep license and copyright notices and state changes you made.

Wtf does this do

octo-smart-summary is a small Go service that reads conversation threads from the OCTO workplace platform and uses an AI language model to produce a structured summary. Instead of leaving team members to manually catch up on long group chats or meeting transcripts, this service distills them into a scannable brief listing key decisions, unanswered questions, and suggested follow-up actions. The service is part of the larger OCTO ecosystem, an open source workplace platform that includes a backend server, task management, mobile clients, and admin tools. When a conversation ID is submitted, the service fetches the transcript from octo-server, breaks it into chunks that fit the AI model's context window while preserving speaker and time boundaries, sends those chunks to the language model with a summarization prompt, parses the structured JSON output, adds participant and duration details, and returns the result. If the model returns malformed JSON, it retries the prompt once. A practical design choice is that the LLM endpoint is fully configurable through an environment variable, so you can point it at any service that speaks the OpenAI chat completions API format: a self-hosted model, a commercial API, or a gateway in between. The output is always structured JSON rather than free-form prose, so other OCTO services such as the task manager can consume it directly without re-parsing text. The service exposes four HTTP endpoints: one for synchronous summarization, one for streaming output, one health check, and one metrics endpoint. It is written in Go and licensed under Apache 2.0.

Yoink these prompts

Prompt 1
Show me how to run octo-smart-summary locally with a self-hosted LLM endpoint.
Prompt 2
Explain the JSON structure this service returns for a conversation summary.
Prompt 3
Help me connect octo-smart-summary's /summarise/stream endpoint to a chat UI.
Prompt 4
Walk me through configuring LLM_API_URL to point at Ollama instead of a commercial API.

Frequently asked questions

wtf is octo-smart-summary?

A Go microservice that uses an LLM to turn long chat threads into structured summaries with decisions, open questions, and follow ups.

What language is octo-smart-summary written in?

Mainly Go. The stack also includes Go, REST API, OpenAI-compatible LLM.

What license does octo-smart-summary use?

Use, modify, and distribute freely, including commercially, as long as you keep license and copyright notices and state changes you made.

How hard is octo-smart-summary to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is octo-smart-summary for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.