Features

Everything your team needs to ship with agents

gild is fast, lightweight, and modern — a native desktop app with a thin Rust shell and all the logic in a local Node core. Here's what you get.

Workspace
A gild is a project workspace
Every gild is a Slack channel gild-<slug> — public or private. Members of the gild are members of the channel, and a single gild can span multiple repos.
  • Multi-repo gilds: one workspace, many repositories
  • Public or private channels — membership is channel membership
  • Plain chat is just normal Slack messages
Agents
Local agent sessions, in their own worktree
Prompt an agent and a new Slack thread is created. Each session runs on your machine in its own git worktree (new worktree + branch by default), with the repo, provider, and model selectable per session.
  • Claude and Codex wired end-to-end; Cursor is on the way
  • Each session is an isolated git worktree off a base branch
  • Per-session provider and model picker
  • Agents read a local filesystem mirror — never your Slack credentials
Persistence
Slack is the source of truth
gild owns no server and no database. The prompt becomes a thread root, valued reasoning becomes replies, and on completion a final reply plus an uploaded transcript file capture full session state — all readable in plain Slack.
  • Dual-channel encoding: message metadata + a hidden fenced block
  • Round-trips and stays human-readable in Slack
  • Transcript file uploaded on finish enables resume
Review
A branch tree with click-to-diff
The right panel shows a session's diff and review, or — for a gild — a tree of active branches and worktrees. Stacked branches render as a tree; click any node to diff it.
  • Worktrees as a DAG; stacked branches as a tree
  • Inline review comments posted back as Slack thread replies
  • Ahead/behind and owning session per node
Team
Resume someone else's session
Because the full transcript lands in Slack, a teammate can rehydrate a finished session into a fresh local worktree from its transcript file and keep going.
  • Hand off work across machines and people
  • Replay the transcript into provider state to resume
  • Recreate the worktree from the recorded base commit
Onboarding
Two ways to connect Slack
Use the shared gild Slack app for a polished one-click flow, or bring your own Slack app and paste tokens for a fully serverless, privacy-first setup. Tokens live in your OS keyring, never on a gild server.
  • Shared app: hosted OAuth callback deep-links the token back via gild://
  • BYO app: paste xoxb-/xoxp-/xapp- tokens; the website is never involved
  • Secrets stay in the OS keyring — never on disk in plaintext