Skip to main content

​
Syntax

tracer create [TITLE] [OPTIONS]

​
Description

Creates a new issue with the specified title and options. Issues are automatically assigned sequential IDs based on your configured prefix.

​
Arguments

​
TITLE
string
required
The issue title. Wrap in quotes if it contains spaces.

​
Options

​
-d, --description
string
Issue description with additional details.
​
-p, --priority
integer
default:"2"
Priority level (0=highest, 4=lowest).
​
-t, --issue-type
enum
default:"task"
Issue type. Valid values: bug, feature, task, epic, chore.
​
-a, --assignee
string
Assign the issue to a specific person or agent.
​
-l, --labels
string
Comma-separated labels to attach to the issue.
​
--deps
string
Comma-separated dependencies. Format: type:id or just id for blocks type.Types: blocks, related, parent-child, discovered-from.
​
--id
string
Explicit issue ID to avoid collisions. Use with caution.
​
-f, --file
string
Create from markdown file (not yet implemented).
​
--json
boolean
Output the created issue in JSON format.

​
Examples

tracer create "Fix login bug"

​
Output Format

​
Human-readable

✓ Created issue bd-42 Fix login bug
  Labels: security, urgent
  Dependencies: blocks:bd-41

​
JSON (with —json flag)

{
  "id": "bd-42",
  "title": "Fix login bug",
  "description": "",
  "design": "",
  "acceptance_criteria": "",
  "notes": "",
  "status": "open",
  "priority": 0,
  "issue_type": "bug",
  "assignee": "",
  "estimated_minutes": null,
  "created_at": "2026-03-04T10:30:00Z",
  "updated_at": "2026-03-04T10:30:00Z",
  "closed_at": null,
  "external_ref": null,
  "dependencies": []
}
Issues are created with status open by default. Use tracer update to change the status to in_progress when you start working on them.
Use the --json flag to capture the issue ID in scripts:
ISSUE_ID=$(tracer create "My task" --json | jq -r '.id')
echo "Created: $ISSUE_ID"

Build docs developers (and LLMs) love

Get started for freeTalk to us