Idea Capture & Management

Ideas are the entry point to the content pipeline: a lightweight, quickly-captured record that gets triaged and — when it's ready — turned into a full LinkedIn post draft.

What you can do

• Capture instantly. The Quick-add bar at the top of the Ideas page takes a single block of free text — no separate title field. Press Enter to save, Shift+Enter for a new line.
• Let AI title it for you. Whatever you type becomes the idea's description; an AI model (Amazon Bedrock) reads it and generates a short, punchy title automatically.
• Filter by status. The status dropdown on the Ideas page narrows the list to New or Converted (or All statuses).
• Edit. Open an idea's edit dialog to revise its title or description.
• Generate a post. Click the lightning-bolt action on any New idea to open the Generate Post dialog — pick a prompt template, audience, tone, language, and length, then generate a draft. This is the one path that moves an idea to Converted.
• Delete. Any idea — including one already Converted — can be deleted.
• Capture from outside the app. A token-based Quick Capture endpoint powers the bookmarklet, Raycast, and other automation entry points without a full login session. See Capturing Ideas.

AI title generation

When you create an idea through the app (or Quick Capture), the text you type is sent to the backend as raw content. The backend calls Bedrock to generate a short, 3-4 word title from it, then stores:

• your original text as description
• the AI-generated text as title

you type:  "Just realized our onboarding flow loses 40% of users at step 3 —
            thinking about writing up what we changed to fix it"
                              │
                              ▼  Bedrock: generate_idea_title(content)
                              │
title  ──▶ "Fixing Onboarding Drop-off"
description ──▶ (your original text, verbatim)

This is why the Quick-add placeholder reads "Describe your idea... AI will generate a short title." — you're never expected to write a title yourself.

Idea lifecycle

An idea has exactly two states:

The only allowed transition is new → converted, and it happens in one of two ways:

1. You generate a post from it — clicking "Generate Post" and completing the generation flow converts the idea as a side effect of creating the post. This is the normal path; the app never exposes a manual "mark as converted" control.
2. A direct API call to PUT /api/ideas/{id}/status — available to API/automation clients, not exposed anywhere in the UI.

There's no way back from converted to new, and no other status exists (an earlier product design sketched out triaged, in_progress, archived, and a priority field — none of that made it into the shipped implementation).

Fields

Where ideas come from

Known gap

The Ideas page ships a multi-select checkbox / "bulk delete" code path in the component tree, but no control in the UI ever populates a selection — it's inert, carried over from an unfinished feature. There is currently no bulk-action capability in the shipped product.

See also

• API Reference → Ideas — the full REST contract.
• MCP → Ideas Tools — using ideas from an AI agent, and how that surface diverges from the REST API.
• Capturing Ideas — Quick Capture setup.
• Getting Started → Pipeline — what happens after an idea becomes a post.