The inbox

The inbox is a lightweight capture-and-triage list. When an idea, a bug, or a stray note shows up mid-flow, drop it in the inbox and keep working — you can decide what to do with it later. It’s the front door for work that isn’t yet a feature or a task.

Capturing items

Click Add idea in the top bar (available from any tool) or + in the inbox view. Each inbox item has a kind:

Give an item a title and press Enter for a quick capture, or click it to open the detail view and add a longer description.

Example: you’re in a code review and notice a performance issue. Click Add idea in the top bar, type “Slow query on user search endpoint — add index”, pick Fix as the kind, and press Enter. Then go back to the review — the issue is captured and you haven’t lost context.

Attachments

An inbox item can carry attachments — pick files from your computer and Bedrock copies them alongside the item (under .bedrock/attachments/). A badge on each row shows how many files are attached, so a spec, a screenshot, or a research note travels with the idea.

Sorting

Sort the inbox list by:

• Newest first (default)
• Oldest
• Title A–Z
• By kind

Triage: promote or archive

When you’re ready to act on an item, promote it:

• Promote to feature — creates a feature card with the item’s title and description pre-filled.
• Promote to task — creates a task card the same way.

Items you don’t need are archived rather than deleted — they disappear from the active list but are kept for reference. Toggle Show archived to see them.

Tips

• Don’t filter yourself at capture time. Write the idea down first, judge it later.
• Use the inbox during meetings or code review to jot things down without switching context. Come back and triage when the session ends.
• Review the inbox at the start of each sprint or release planning session — sweep through, archive stale items, and promote the ones worth doing.
• Attachments on inbox items carry through to the promoted feature or task.