--- id: create title: bd create slug: /cli-reference/create sidebar_position: 10 --- Generated from `bd help --doc create` ## bd create Create a new issue (or batch from markdown/graph JSON) ``` bd create [title] [flags] ``` **Aliases:** new **Flags:** ``` --acceptance string Acceptance criteria --append-notes string Append to existing notes (with newline separator) -a, --assignee string Assignee --body-file string Read description from file (use - for stdin) --context string Additional context for the issue --defer string Defer until date (issue hidden from bd ready until then). Same formats as --due --deps strings Dependencies in format 'type:id' or 'id' (e.g., 'discovered-from:bd-20,blocks:bd-15' or 'bd-20') -d, --description string Issue description --design string Design notes --design-file string Read design from file (use - for stdin) --dry-run Preview what would be created without actually creating --due string Due date/time. Formats: +6h, +1d, +2w, tomorrow, next monday, 2025-01-15 --ephemeral Create as ephemeral (short-lived, subject to TTL compaction) -e, --estimate int Time estimate in minutes (e.g., 60 for 1 hour) --event-actor string Entity URI who caused this event (requires --type=event) --event-category string Event category (e.g., patrol.muted, agent.started) (requires --type=event) --event-payload string Event-specific JSON data (requires --type=event) --event-target string Entity URI or bead ID affected (requires --type=event) --external-ref string External reference (e.g., 'gh-9', 'jira-ABC', Linear URL) -f, --file string Create multiple issues from markdown file --force Force creation even if prefix doesn't match database prefix --graph string Create a graph of issues with dependencies from JSON plan file --id string Explicit issue ID (e.g., 'bd-42' for partitioning) -l, --labels strings Labels (comma-separated) --metadata string Set custom metadata (JSON string or @file.json to read from file) --mol-type string Molecule type: swarm (multi-agent), patrol (recurring ops), work (default) --no-history Skip Dolt commit history without making GC-eligible (for permanent agent beads) --no-inherit-labels Don't inherit labels from parent issue --notes string Additional notes --parent string Parent issue ID for hierarchical child (e.g., 'bd-a3f8e9') -p, --priority string Priority (0-4 or P0-P4, 0=highest) (default "2") --repo string Target repository for issue (overrides auto-routing) --silent Output only the issue ID (for scripting) --skills string Required skills for this issue --spec-id string Link to specification document -s, --status string Initial status --stdin Read description from stdin (alias for --body-file -) --title string Issue title (alternative to positional argument) -t, --type string Issue type (bug|feature|task|epic|chore|decision|spike|story|milestone); custom types require types.custom config; aliases: enhancement/feat→feature, dec/adr→decision (default "task") --validate Validate description contains required sections for issue type --waits-for string Spawner issue ID to wait for (creates waits-for dependency for fanout gate) --waits-for-gate string Gate type: all-children (wait for all) or any-children (wait for first) (default "all-children") --wisp-type string Wisp type for TTL-based compaction: heartbeat, ping, patrol, gc_report, recovery, error, escalation ```