Azad Board · IA sweep · v0.1 · 2026-05-28

A control room for
humans + agents.

Azad Board is Slack and Discord, with the agent workspace built in. People talk in channels. From any channel, anyone can spawn an agent task that runs against a connected GitHub repo, posts updates back into chat, and opens its own VS Code-style workspace when you want to dive in.

This first pass sweeps the full information architecture — 9 screens spanning desktop and mobile.

Direction
Modern minimal · Linear / Vercel · dark
Surface
Desktop web primary · Mobile chat-only
Type
Inter display + body · JetBrains Mono
Accent
oklch(70% 0.17 262) — soft indigo
Density
Information-dense, dev-tool register
▸ How I read your brief

The core insight: tasks always belong to exactly one channel, but anything else — agent providers, subscriptions, repos, files — can be shared at the user, org, or channel level. The IA snaps to that: a channel is the home for both human conversation and the agent tasks born from it, and a task is a first-class object that lives both inline in chat (as a card) and in its own dedicated workspace.

A few opinions baked into this pass, ready to be redirected: (1) the org rail is left of the channel sidebar (Discord pattern) — your existing screenshot only shows one org, so I extended it for multi-org membership without changing the channel column. (2) agent tasks get their own right rail in the chat view so members see what's in-flight without scrolling chat history. (3) the agent workspace is full-bleed VS Code-style — file tree, diff viewer, terminal, and an agent-conversation panel that doubles as a steering wheel. (4) subscription ↔ provider pairing is explicit so users can BYOK a fallback while still using shared org credits as the default.

IA Information architecture
▸ Org rail (left edge)
Personal org (default) Joined orgs (↕ reorderable) + Create / join Discover orgs
▸ Channel sidebar
Search · Inbox · My tasks · Settings Channels list (public + private) Direct messages Org switcher (top, expands rail)
▸ Channel surface (tabs)
Chat (messages + inline tasks) Tasks (grouped by status) Files Repos (GitHub attached) Members
▸ Agent task lifecycle
Spawn from chat or rail Bound to ONE channel Runs in dedicated workspace Posts updates back to chat Lands as PR · merges in main
▸ Configuration (scopes)
Personal · agent + subscription defaults Org · shared subscriptions + routing rules Channel · overrides for sensitive repos
▸ Management
Org settings (members, repos, policies) Channel settings (repos, perms) Audit log Billing & usage
01 Hero — the rooms where work happens 2 screens
★ Channel — chat Open full
Channel chat /channel-chat.html
4-pane workspace — org rail, channel sidebar, chat thread, agent-task rail. Every channel doubles as the meeting room and the situation room for the agents working there. Inline task cards keep PRs and running agents legible without leaving the conversation.
primary surface Discord/Slack ergonomics inline agent tasks right rail · live runs
★ Agent workspace Open full →
Agent workspace /agent-workspace.html
VS Code-style. File tree, diff viewer, live terminal, and a conversation panel that's both a watch-mode and a steering wheel — interrupt, redirect, or approve next-step.
the killer screen step progress tool calls
02 Channel tabs — same room, different views 2 screens
Channel · Tasks tab Open full →
Channel tasks /channel-tasks.html
Every agent task in this channel — grouped by status, filterable by owner / provider / repo. List, board, or timeline view. The "Tasks" tab next to "Chat" is what makes a channel a real collaboration surface.
Channel · Repos tab Open full →
Channel repos /channel-repos.html
Attached GitHub repos with PRs, recent commits, CI state, and a count of how many agent tasks are currently active against each. Repos can attach at the channel or org level.
03 Flows — starting work + configuring it 2 screens
Flow · New agent task Open full →
New agent task /new-task.html
Prompt on the left, scope on the right. The channel binding is explicit and locked — tasks always belong to exactly one channel — so the rest of the form picks provider, subscription, base branch, and permissions.
Config · Agents + subscriptions Open full →
Agent + subscription setup /agent-config.html
The pairing screen — agent providers (azad / claude code / codex) on top, the subscriptions that power them below. Routing rules on the bottom decide which pairing wins for which task. Scoped tabs at top switch between personal, org, and per-channel overrides.
04 Management + discovery 2 screens
Org · Members & roles Open full →
Org settings /org-settings.html
Multi-section settings: members & roles (shown), channels, GitHub, agent providers, subscriptions, permissions, audit log, billing. The same shell handles channel-level management with a narrower nav.
Discover orgs Open full →
Discover orgs /discover.html
Three on-ramps in one: search public orgs, paste an invite code, accept pending invites. Featured orgs run their agents publicly so newcomers can shadow real work before joining.
05 Mobile — chat-first companion 1 screen
iPhone · Channel chat Open full →
Mobile chat /mobile-chat.html
Per your brief — mobile is for chat, not for running the full agent workspace. You can still read task updates inline, tap to view a task summary, and post a "approve next step" reply from anywhere. Full diff viewing punts to desktop.
▸ Where to take this next
Each of these screens can become a deep-dive in its own pass. Likely next stops:
  • · Task inbox — every task that needs your decision, across orgs.
  • · Org dashboard — usage, budgets, who's burning subscription credits.
  • · Agent provider deep-dive — tool permissions, sandbox rules.
  • · Notifications + inbox — separate mention / approval / merge feeds.
  • · Onboarding — first-run: install GH app, pick provider, run a starter task.