sallaumen/dsh-superagent-superboard

A live operations desk for work that starts on GitHub. The external DeepSeek
Super Agent executes tickets; this Elixir board makes the work visible, keeps
the human in control of consequential actions, and connects GitHub, local
executors, voice, and usage in one place.
Architectural illustration. The screen is a stylized preview of the board;
real interface captures are kept with the UI audits.
The version badges reflect the CI toolchain and the checked-in dependency lockfile; update them when those change.
## What you can do
| In the board | Why it matters |
| Follow issues, pull requests, reviews, checks, and agent tickets across repositories | See what is running, queued, blocked, or waiting for you without piecing together several screens |
| Turn a request into GitHub tasks and coordinate Claude Code or Codex locally | Keep the chosen executor, spending limits, and confirmation in the same workflow |
| Ask questions, dictate requests, and hear status | Use browser speech or optional ElevenLabs voice, with confirmation before consequential actions |
| Review daily summaries, activity, and usage by source | Understand what changed and where time and model usage went |
The board starts in English. Settings → Language switches this browser to
Brazilian Portuguese; spoken language is a separate preference.
## How the pieces fit
mermaid
flowchart LR
H["Human"] -->|"request or confirmation"| B["Board Phoenix LiveView"]
G["GitHub issues · PRs · checks"] -->|"mention"| A["DeepSeek Super Agent separate process + worktrees"]
A -->|"ticket reports and PRs"| G
B -->|"syncs work"| G
B -->|"reads ticket state"| A
B -->|"confirmed dispatch"| E["Claude Code / Codex"]
E -->|"PR"| G
GitHub is the shared record. The agent watches mentions, works in isolated
worktrees, and reports back through issues and PRs. The board mirrors that work,
offers actions through a recorded confirmation gate, and can dispatch local
executors. Stopping the board does not stop the separate agent. See
the agent loop and the
architecture map.
## Quick start
The project uses Elixir 1.19 / Erlang OTP 27 in CI and PostgreSQL 16.
The development database is configured at 127.0.0.1:5434 with user board,
password board, and database agent_board_dev.
If you need a local PostgreSQL instance, one option is:
sh
docker run --name dsh-board-postgres \
-e POSTGRES_USER=board -e POSTGRES_PASSWORD=board \
-e POSTGRES_DB=agent_board_dev -p 5434:5432 -d postgres:16
Then:
sh
git clone https://github.com/sallaumen/dsh-superagent-superboard.git
cd dsh-superagent-superboard
cp .env .env.local
# Add a GITHUB_TOKEN to .env.local for repositories you want to sync.
mix setup
PORT=4002 mix phx.server
Open http://127.0.0.1:4002. mix setup installs dependencies, creates and
migrates the development database, seeds it, and builds assets. AI and ElevenLabs
keys in .env.local are optional; without a configured AI provider, AI requests