Enum Commands 

pub enum Commands {
    Plan {
        format: String,
    },
    Log {
        event_type: LogEventType,
        message: String,
        task: Option<i64>,
        format: String,
    },
    Search {
        query: String,
        tasks: bool,
        events: bool,
        limit: Option<i64>,
        offset: Option<i64>,
        since: Option<String>,
        until: Option<String>,
        format: String,
    },
    Init {
        at: Option<String>,
        force: bool,
    },
    Dashboard(DashboardCommands),
    Doctor,
    Status {
        task_id: Option<i64>,
        with_events: bool,
        format: String,
    },
    Task(TaskCommands),
    Suggestions(SuggestionsCommands),
    Config(ConfigCommands),
}

Variants

Plan

Create or update task structures declaratively

Fields

format: String

Output format (text or json)

Log

Record events (decisions, blockers, milestones, notes)

Quick event logging for the current focused task or a specific task.

Examples: ie log decision “Chose JWT authentication” ie log blocker “API rate limit hit” –task 42 ie log milestone “MVP complete” ie log note “Consider caching optimization”

Fields

event_type: LogEventType

Event type: decision, blocker, milestone, note

message: String

Event message (markdown supported)

task: Option<i64>

Target task ID (optional, uses current focused task if not specified)

format: String

Output format (text or json)

Search

Unified search across tasks and events

Smart keyword detection:

• Query with ONLY status keywords (todo, doing, done) → filters by status
• Query with other words → uses FTS5 full-text search

Status filter examples (returns tasks with matching status): ie search “todo doing” # All unfinished tasks (AI session start) ie search “todo” # Only todo tasks ie search “done” # Only completed tasks

FTS5 search examples (full-text search): ie search “JWT authentication” ie search “API AND client” ie search “blocker” –events –no-tasks

Fields

query: String

Search query: status keywords (todo/doing/done) or FTS5 syntax

tasks: bool

Search in tasks (default: true)

events: bool

Search in events (default: true)

limit: Option<i64>

Maximum number of results (default: 20)

offset: Option<i64>

Result offset for pagination (default: 0)

since: Option<String>

Filter by start time (e.g., “7d”, “1w”, “2025-01-01”)

until: Option<String>

Filter by end time (e.g., “1d”, “2025-12-31”)

format: String

Output format (text or json)

Init

Initialize a new Intent-Engine project

Creates a .intent-engine directory with database in the current working directory.

Examples: ie init # Initialize in current directory ie init –at /my/project # Initialize at specific directory

Fields

at: Option<String>

Custom directory to initialize (default: current directory)

force: bool

Re-initialize even if .intent-engine already exists

Dashboard(DashboardCommands)

Dashboard management commands

Doctor

Check system health and dependencies

Status

Show current task context (focus spotlight)

Displays the focused task with its complete context:

• Current task details (full info)
• Ancestors chain (full info)
• Siblings (id + name + status)
• Descendants (id + name + status + parent_id)

Examples: ie status # Show current focused task context ie status 42 # Show task 42’s context (without changing focus) ie status -e # Include event history

Fields

task_id: Option<i64>

Task ID to inspect (optional, defaults to current focused task)

with_events: bool

Include event history

format: String

Output format (text or json)

Task(TaskCommands)

CRUD operations on individual tasks

Direct task manipulation commands for creating, reading, updating, and deleting tasks, plus workflow shortcuts (start, done, next).

Examples: ie task create “Implement auth” –description “JWT-based auth” ie task get 42 –with-context ie task list –status todo ie task start 42 ie task done ie task next

Suggestions(SuggestionsCommands)

Manage LLM-generated suggestions

View and dismiss suggestions generated by background analysis. Suggestions include task structure reorganization hints and analysis errors.

Examples: ie suggestions list ie suggestions dismiss 5 ie suggestions dismiss –all ie suggestions clear

Config(ConfigCommands)

Configuration management (key-value store)

Manage configuration settings stored in the project database. Used for LLM endpoints, API keys, and other project-level settings.

Examples: ie config set llm.endpoint “http://localhost:8080/v1/chat/completions” ie config get llm.api_key ie config list –prefix llm ie config unset llm.model

Trait Implementations

impl Clone for Commands

fn clone(&self) -> Commands

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl FromArgMatches for Commands

fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

fn update_from_arg_matches_mut<'b>( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

impl Subcommand for Commands

fn augment_subcommands<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate Self via FromArgMatches::from_arg_matches_mut

fn augment_subcommands_for_update<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate self via FromArgMatches::update_from_arg_matches_mut

fn has_subcommand(__clap_name: &str) -> bool

Test whether Self can parse a specific subcommand