Trundle
Trundle
Trundle
Back to docs
Getting Started

Quick start guide

Set up Trundle and run your first ticket

Connect your workspace, add the context your team already relies on and see how work moves from ticket to done

Back to docs
Getting Started

Quick start guide

Set up Trundle and run your first ticket

Connect your workspace, add the context your team already relies on and see how work moves from ticket to done

Overview

Trundle keeps the decisions, files and people behind the work attached to the ticket. This guide takes you from a new workspace to a first ticket ready for the team.

Set up your workspace

  • Create an account: Sign up with "Continue with Google", or with your name, email and a password (you'll add your company details and confirm a verification code).
  • Connect GitHub: Grant Trundle access to the repositories you want the Trundle Dev Agent to work within.
  • Create a project: Give it a name and select at least one repository. You can optionally set a base branch (it defaults to the repository's default branch) and a project goal.

Build your Knowledge Base

  • Upload context: Add PRDs, design docs, transcripts and notes to a project's Knowledge tab. Many file types are supported (PDF, Office documents, text/Markdown, images, code files), up to 20 MB each.
  • Embeddings: Trundle embeds what you upload so its agents can use it as context for generating and reviewing code.
  • Ask questions: Use Ask Trundle to ask your documentation questions in natural language and get answers grounded in your own material.

Run your first ticket

  • Auto-generate tickets: Give Trundle a description of at least 250 characters and it will generate a full set of tickets in the background.
  • Improve tickets with AI: On a manual ticket, use "Improve with AI" to rewrite the description, and the separate "Ask clarifying questions" action to raise and answer open questions (both need a title and at least ~100 characters).
  • Set the execution scope: Choose which stages Trundle runs for a ticket: code (write the change), review, and qa, assigning each stage to Trundle or to your team.
Trundle

Work moves better when everyone can see where it is going.

Trundle

Work moves better when everyone can see where it is going.

Trundle

Work moves better when everyone can see where it is going.