Back to directory

flowboard

In a curated listMaintenance: Maintained

juntaoding/flowboard

Open-source office collaboration & team management inside DSH: goals, meetings, people, agent execution, progress and documents in one workflow; bundled Whisper transcription

View on GitHub
$ dsh plugin add flowboard

Install

dsh has no central install command — add this plugin’s entry (documented in its README) to your profile or patch config, then restart.

How installs work

12

stars

0

forks

TypeScript

Language

MIT

License

2026-08-17

Created

2026-08-17

Last push

README

Flowboard

English | 简体中文

Let work happen naturally in the Harness while keeping the team aligned without extra management overhead.

Flowboard is an open-source office collaboration and team management plugin for DeepSeek Harness (DSH). It brings goals, meetings, people, agent execution, progress, and documents into one coherent workflow, so work can move continuously from discussion to execution and shared knowledge. Tasks are not the boundary of the product; they are the backbone that supports this way of working.

Alpha: 0.1.2-alpha.5 is still at an early validation stage. APIs, data structures, and installation procedures may change incompatibly. It is intended for local evaluation and small-team trials, not stable production deployments.

Management Without the Busywork

Traditional task management makes employees do the same work twice: first they meet, communicate, and execute, then they open another system to create tasks, assign owners, update progress, and organize documents. The management system records a manually maintained copy of the work rather than the work itself. As soon as people stop updating it, the board becomes inaccurate.

AI-assisted work makes this problem even more visible. People already use agents in the Harness to research, write, analyze, plan, and execute. If those results remain in individual sessions, the team still cannot see who is doing what, how work is progressing, or what has been produced. Someone eventually has to copy the information and report it manually.

Flowboard changes how task information is created:

  • When work begins, goals and meeting action items become tasks, owners, and plans.
  • While work is in progress, members and agents execute and update progress in the same task context.
  • When work is completed, documents, decisions, and supporting material return to the original task and project.
  • When the team collaborates, every member and agent reads the same authoritative state and continues from there.

People still complete tasks, but no longer have to manage a separate copy of them. Management happens as the work happens.

One Operating Model Across the Harness

The Harness is where people and agents work. Flowboard provides its collaboration and organizational memory layer. Goals set direction, meetings create alignment, people and agents execute together, progress stays current, and documents preserve the outcome. Tasks connect these stages instead of becoming a form that employees must maintain outside their conversations.

An employee sets a goal / the team holds a meeting
                         ↓
The Harness agent understands intent and existing context
                         ↓
Flowboard creates tasks, ownership, plans, and linked documents
                         ↓
Members and agents continue execution in their own sessions
                         ↓
Progress, issues, documents, and decisions return to one task context
                         ↓
The next member or agent continues from the actual state of the work

DSH remains responsible for sessions, models, agents, and the plugin lifecycle. Flowboard does not create a second agent entry point or make DSH depend on a standalone application. Users install only @flowboard/dsh; the UI and agents then share the same FlowboardService, data, and authorization rules.

How a Complete Workflow Unfolds

Consider a product meeting:

  1. Before the meeting: A member asks an agent to read project progress, incomplete tasks, and related documents, then assemble the meeting context.
  2. During the meeting: Flowboard segments audio locally in the browser and transcribes it with the bundled Whisper runtime. The meeting Supervisor continuously identifies action items, decisions, risks, and supporting material.
  3. Live revisions: “Assign it to Alex,” “No, change that to Sam,” and “Finish it by next Wednesday” are understood as successive revisions to one intent rather than three duplicate tasks.
  4. After the meeting: Tasks, owners, due dates, decisions, risks, the meeting summary, and linked documents are already part of the project. No second round of manual data entry is needed.
  5. Continued execution: The owner returns to their Harness session and asks an agent to research, write, or execute. Task status and outputs continue to accumulate in the original context.

Managers see state produced by the work itself, not a status report filled in afterward.

What You Get

Capability What it changes
AI-native office collaboration Agents can read team context and connect goals, meetings, tasks, and documents without employees transcribing everything into another system.
Jira-style project boards Manage tasks with workflows such as To Do, In Progress, and Done, including drag and drop, assignees, priority, progress, and due dates.
Multidimensional task tables View and edit tasks in a dense table with custom text, number, date, single-select, multi-select, and people fields.
AI meeting secretary Browser VAD, local Whisper, live transcription, intent revision, persisted action items, and post-meeting summaries form a complete workflow.
Documents and organizational memory Markdown documents can be linked to projects, meetings, and tasks, allowing agents to follow the history and rationale behind the work.
Personal and team perspectives My Tasks, personal boards, personal calendars, and project workspaces share the same business facts instead of duplicating data.
Authorization and auditability Writes from both the UI and agents pass through authorization, runtime validation, idempotency, optimistic locking, transactions, versioning, and audit logs.

Quick Start

Requirements

Read the full README on GitHub →

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.