Creating a Slice

A "slice" is Brie's term for a bug report. Each slice bundles your captures (screenshots, video, session replay) with automatically collected technical context into a single, shareable package.

From a capture

The most common way to create a slice is directly from a capture:

  1. Take a screenshot or record a video.
  2. Click Edit on the preview dialog to open the annotation editor.
  3. Add annotations if needed.
  4. Fill in the details in the right side panel (title, description, priority, workspace, etc.).
  5. Click Create Link.

Brie packages your capture with console logs, network data, and device info into a single slice and opens it in a new tab.

Slice details

The annotation editor's side panel lets you fill in the following:

Title — Click the title at the top of the editor to rename it (defaults to "Untitled report"). Max 50 characters.

Description — A text field for describing the bug and how to reproduce it. Max 512 characters.

Priority — Choose from:

  • Highest (red)
  • High (orange)
  • Medium (yellow)
  • Low (green, default)

Labels — Add up to 6 short tags to categorize the bug (e.g., "ui", "login", "regression").

Workspace & space

Workspace — Use the workspace selector in the editor header to choose which workspace this slice belongs to. Defaults to your default workspace. You can switch to any workspace in your organization, or create a new one.

Space — A space is a folder within a workspace, used to group related slices (e.g., by feature, sprint, or project area). Optionally assign the slice to a space. Click the folder icon to pick an existing space or create a new one. Spaces help you organize slices by project area, feature, or sprint.

Attaching files

Click the paperclip icon to attach additional files to your slice — documents, logs, HAR files, or anything else that helps describe the bug. You can attach multiple files. Each attached file appears in a list below the button, and you can remove individual files before submitting.

Sharing options

When creating a slice, you can choose how to share it:

  • Create a link — Generates a shareable URL for the slice.

Issue tracker integrations (Linear, Jira, Azure DevOps) are coming soon and will allow you to push slices directly to your project management tools.

What happens next

Once your slice is created, Brie's agent immediately starts working — it analyzes the bug context, examines your codebase, and prepares a code fix proposal. By the time you open the slice in the web app, a Suggested Changes panel is already waiting for your review. Approve it, and Brie creates a pull request on your behalf. See Agentic Fix Suggestions for details.

Pro tip: The more context Brie captures (screenshots, console errors, network data), the more accurate the suggested fix will be.