Gorka Molero

Public · agent workflow

Claude-on-Discord

A full developer-agent workspace that runs Claude Code from Discord threads, keeps work isolated in coding lanes, and makes agent activity reviewable.

Public repo Discord agent workflow README upgraded

Problem

Coding agents are powerful but awkward when their work is hidden in a local terminal. A team needs clear lanes, visible tool events, branch/worktree separation, and a way to request work from the same collaboration surface where decisions happen.

What I Built

Claude-on-Discord turns Discord into an agent operations layer. Threads become scoped work sessions, commands start or continue Claude Code runs, tool events stream back to the channel, and repository work is organized around branches and worktrees.

Interaction surface Discord threads, commands, progress messages, and tool-event streaming.
Execution model Claude Code sessions, repository selection, isolated worktrees, and branch-aware actions.
Review loop Agent output stays visible enough for inspection, handoff, and PR-oriented follow-through.
Claude-on-Discord architecture diagram showing Discord surface, session router, work lane, Claude Code run, review stream, human handoff, and guardian supervisor.
Public-safe operations diagram grounded in the local source and architecture docs. It shows the agent workflow without exposing Discord server data, tokens, channel IDs, private messages, or local paths.
Sanitized Claude-on-Discord disposable thread transcript showing fork command, worktree lane, live tool stream, diff handoff, PR handoff, typecheck, tests, and distribution check.
Sanitized disposable-thread transcript. It shows the runtime shape for thread branching, worktree handoff, tool-event streaming, diff review, and PR flow without exposing Discord ids, bot tokens, server names, private prompts, local paths, or live repo output.
Public-safe Claude-on-Discord live tool stream contract grounded in source modules and integration tests.
Source-grounded tool-stream contract. It maps the Discord request, queued Claude Code run, stream events, live tool trace, review card, and expand/collapse controls covered by the local integration tests.

System Architecture

Technical Decisions

  • Use Discord threads as durable, human-readable session containers.
  • Keep agent execution tied to explicit repository and worktree state.
  • Surface progress and tool events instead of treating the agent as a black box.
  • Preserve a path from request to implementation to review instead of stopping at chat.

What This Proves

This is practical agentic tooling: not a demo chatbot, but infrastructure for delegating real coding tasks, managing concurrent work, and keeping a human reviewer in the loop.