Features

What Braid does today, grouped by what you want to do. Where something needs setup, is a pilot, or has a limit, it says so.

Boards and tickets

Track work in Braid from day one, or sync with Plane or Jira.

Works with your tracker
  • Built-in ticketsCreate, comment, assign, set dates, edit titles and drag between columns. References like GEN-1.
  • Editable columnsAdd, rename, reorder and remove columns. Removing a column that has tickets asks where they go.
  • Live boardsWhen someone else moves a ticket, your board updates without a reload.
  • Hand a ticket to an agentStart a session from a ticket. On built-in boards the agent's moves apply at once.
  • PlaneTwo-way sync by webhook and a five-minute poll. Agent moves wait for your approval.
  • JiraNeeds setup or has limitsTwo-way sync by a five-minute poll.
  • Pull requests on ticketsA ticket reference in a PR title, branch or body links it to the ticket, and a Pull requests panel shows its state and CI. Needs the GitHub integration and the repository webhook pointed at Braid.
  • Ticket followersA session follows tickets it raised, and can post their moves back to a Slack thread.
  • Schedule work on a ticketPick an agent, write an instruction, run once or repeat.

Agent teams

A lead agent breaks work into tasks and hands them to other agents.

Task breakdown with agent teams
  • Lead agentsAn agent marked lead-capable can coordinate others. New organisations get one.
  • Task lists and sub-sessionsEach task runs in its own sub-session with only the context it needs, and a synthesis step merges the results.
  • Watch and steerA task graph, per-task status, Hold and Release, and a button into any sub-session.
  • ValidatorsA task can name a validator agent, and only completes when it passes.

Decisions

What waits for a person.

Decisions
  • Decision cardsA card in the conversation, a Decisions panel, and a Needs action item in your Inbox. Approve, reject, choose or acknowledge.
  • Secrets and credentialsAn agent asks for a secret or credential; a person approves or provides it.
  • External ticket movesOn Plane and Jira boards, an agent's ticket move is a proposal you approve.
  • Publishing an automationPublishing is a decision that carries the diff.
  • No self-approvalAgents can only create soft gates. Hard gates come from the system.

Goals

An outcome you own that Braid keeps working towards. A pilot, switched on by an org admin.

Goals (pilot)
  • Plan and delegationPilotA written plan, a graph of plan items, tickets raised and handed to your lead, through to a pull request a person merges.
  • A loop that keeps workingPilotReviews on a cadence, extra runs when something sticks, and retries failures by itself.
  • Talk to itPilotTell the goal the date moved and it writes a new plan version and says what changed.
  • Done whenPilotDescribe done in words; Braid turns it into conditions checked against real data, and asks you only when they hold. Its own switch, Judged end states.
  • ControlsPilotPause, resume, stop, review now, and an admin Pause all goals.
  • Member-owned goalsPilotMembers can create and own goals within what they may already do, while admins keep oversight. Off unless an admin switches it on.

Automations, watches and the calendar

Write the rule in a sentence, read the steps, test them, then switch it on.

Automations
  • Automations from plain wordsCompile a sentence into a step graph that uses your agents and integrations. Org admins build them.
  • Tests before it runsTrigger payloads, step stubs, replay of recent events, determinism check and dry run.
  • Schedules and calendarOnce, daily, weekly, monthly or yearly, with a calendar of runs, deadlines and dated tickets.
  • QueuesDurable backlogs between automations, with retries, dead letters and requeue.
  • Watches and alertsSay what you expect by a date. A missed one becomes an alert in your Inbox and on your phone.
  • Member automationsAn agent proposes a recurring job in a session; you approve it.

Agents and the Workbench

A working team on day one, and a place to change it safely.

Any model, one team
  • A starting teamEvery new organisation gets a lead, an assistant and guidance they already read.
  • Create and edit agentsHandle, role, model, harness, tools, repository and personality. Org admins only.
  • See the exact promptThe Compiled view shows what the agent will receive, with sizes.
  • Draft mode and scratch testsEdit, try it in a throwaway conversation, then commit or discard.
  • Choose the runtime per agentNeeds setup or has limitsClaude Code, Codex or OpenCode, chosen per agent. OpenCode reaches models from many providers.
  • People directoryOne person record across Braid, Slack, Plane, Jira and GitHub.

Knowledge

Documents agents read, edited in Braid.

KnowledgeAgents that learn
  • Choose what each agent is givenGive a document to the organisation, a board, every agent, named agents or no one yet.
  • Prompt or on requestShort documents go into the prompt; long ones are fetched when needed.
  • Preview what an agent getsPreview shows exactly what an agent would be given.
  • HistoryNeeds setup or has limitsEvery revision with its author. No restore button yet.
  • Held changesAn agent's change that would widen who is given a document waits for a person.
  • Start from a fileDrop a Markdown or text file, up to 256 KB.

Integrations and identity

Give each agent only what it needs.

Integrations and identity
  • MarketplaceContentful, Plane, Slack, HubSpot, GitLab, Atlassian, Mailgun, Inbound Webhook, PostgreSQL, Outline, Google Workspace, S3-compatible storage, GitHub, Stripe, and Linear (tools only).
  • Per-agent accessEach agent gets only the integrations it is allowed, one tool server per integration.
  • Bring any MCP serverAdd a Custom MCP Server with a URL and auth.
  • Read-only databasePostgreSQL with Enforce read-only.
  • GitHub as yourselfNeeds setup or has limitsConnect GitHub as yourself and choose who authors pull requests. The agent must be granted get_github_token to open one.
  • Secrets and git identitiesName a secret, say which agents may read it; create SSH git identities for pushes.

Organisation and plans

Sign-in, people and limits.

Organisation and plans
  • Sign-up and passkeysInvite only during the closed beta. Sign in with Google, GitHub, Microsoft or OIDC, and add a passkey.
  • Set up your organisationA checklist computed from real state, for admins.
  • Invites, roles and domainsInvite by email, admin and member roles, and a verified email domain that lets colleagues join.
  • Several organisationsAn org switcher; the desktop app runs a supervisor per membership.
  • Works on a phoneNeeds setup or has limitsAn installable web app. The agents roster and Workbench are not in the phone menu yet.
  • Plan and usageEach limit as used over maximum. During the beta every organisation is on Teams.

Not yet

Things people ask about that Braid does not do today.

  • A Windows desktop app
  • GitHub Issues or Linear as a board's tracker
  • Private sessions
  • Sharing a goal with viewers
  • Exporting knowledge
  • Email, Microsoft Teams or Discord as ways in