:LovelaceTaskStatus

Get detailed status information and results for a specific task.

Command Signature

vim

:LovelaceTaskStatus <task_id>

Alias: :LTaskStatus

Arguments:

task_id (required) - The task identifier (e.g., task_abc123def456)

Description

The :LovelaceTaskStatus command retrieves comprehensive status information for a specific task, including current state, progress updates, agent assignment, execution timeline, and final results.

What it shows:

Task state (queued, running, completed, failed)
Agent worker assignment
Progress notifications timeline
Execution duration
Final results or error messages
File changes and diffs

When to use:

Checking progress of long-running tasks
Viewing detailed results after completion
Debugging task failures
Monitoring task execution timeline
Reviewing file changes before applying

Usage

Basic Usage

vim

:LovelaceTaskStatus task_abc123def456

Opens a split window with detailed task information.

Get Task ID

First, find the task ID from the tasks list:

vim

:LovelaceTasks
" Copy task ID from the output
" Example: task_abc123def456

:LovelaceTaskStatus task_abc123def456

From Lua

lua

require("lovelace.commands").task_status("task_abc123def456")

Output Format

The status buffer displays comprehensive task information:

# Task Status: task_abc123def456

## Overview
- **Description**: "Refactor authentication flow to use async/await"
- **Status**: Running
- **Agent**: 550e8400-e29b-41d4-a716-446655440000
- **Created**: 2025-12-28 14:30:00
- **Duration**: 45s

## Progress Timeline
[14:30:05] Started: Analyzing authentication code...
[14:30:12] Progress: Identifying async/await conversion opportunities...
[14:30:28] Progress: Generating refactored code...
[14:30:35] Progress: Running validation checks...
[14:30:45] Progress: Creating file diffs...

## Results
Status: In progress

Press 'q' to close

Task State Details

Queued State

# Task Status: task_abc123

## Overview
- **Status**: Queued
- **Agent**: (pending)
- **Created**: 2025-12-28 14:25:00
- **Duration**: 30s

## Queue Position
Position: 2 of 5

## Waiting Reason
All agents currently busy. Task will start when an agent becomes available.

What it means:

Task submitted successfully
Waiting for available agent worker
Shows position in queue
Automatic pickup when agent available

Action: Wait for agent assignment, or check agent capacity with :LovelaceAgents

Running State

# Task Status: task_abc123

## Overview
- **Status**: Running
- **Agent**: 550e8400-e29b-41d4-a716-446655440000
- **Created**: 2025-12-28 14:30:00
- **Duration**: 2m 15s

## Progress Timeline
[14:30:05] Started: Analyzing code structure...
[14:30:30] Progress: Generating changes...
[14:31:45] Progress: Running validation...

## Current Activity
Validating generated code against test suite

What it means:

Agent actively executing task
Progress updates show current phase
Duration shows elapsed time
Can monitor progress in real-time

Action: Wait for completion, monitor progress updates

Completed State

# Task Status: task_abc123

## Overview
- **Status**: Completed
- **Agent**: 550e8400-e29b-41d4-a716-446655440000
- **Created**: 2025-12-28 14:30:00
- **Completed**: 2025-12-28 14:35:00
- **Duration**: 5m 0s

## Progress Timeline
[14:30:05] Started: Analyzing code structure...
[14:30:30] Progress: Generating changes...
[14:32:15] Progress: Running validation checks...
[14:34:50] Completed: 3 files changed

## Results
✓ Task completed successfully

### Files Changed
- src/auth/login.ts (45 lines modified)
- src/auth/session.ts (32 lines modified)
- src/auth/types.ts (12 lines added)

### Summary
Refactored authentication flow to use async/await patterns.
All authentication functions now properly handle asynchronous operations
with try-catch error handling.

### Next Steps
1. Review the changes in each file
2. Run test suite to verify functionality
3. Commit changes if satisfied

Press 'q' to close

What it means:

Task finished successfully
All file changes listed
Summary of what was accomplished
Results ready for review

Action: Review results, inspect file changes, apply or reject

Failed State

# Task Status: task_abc123

## Overview
- **Status**: Failed
- **Agent**: 550e8400-e29b-41d4-a716-446655440000
- **Created**: 2025-12-28 14:30:00
- **Failed**: 2025-12-28 14:32:30
- **Duration**: 2m 30s

## Progress Timeline
[14:30:05] Started: Analyzing code structure...
[14:30:30] Progress: Generating changes...
[14:32:15] Error: Validation failed
[14:32:30] Failed: Task execution error

## Error Details
Validation Error: Generated code contains syntax errors in src/auth/login.ts

Error message:
  Unexpected token 'await' on line 45. Async function required.

## Troubleshooting
1. Check that the file exists and is accessible
2. Verify the task description was clear and specific
3. Try resubmitting with more detailed requirements
4. Check agent logs for additional context

Press 'q' to close

What it means:

Task failed during execution
Error details explain what went wrong
Progress timeline shows where failure occurred
Troubleshooting steps provided

Action: Review error message, adjust requirements, resubmit task

Information Fields

Task Metadata

Field	Description	Example
Description	Your original task description	"Add error handling"
Status	Current state	`Running`, `Completed`
Agent	Assigned agent worker UUID	`550e8400-e29b...` or `(pending)`
Created	Task submission timestamp	`2025-12-28 14:30:00`
Completed	Completion timestamp (if finished)	`2025-12-28 14:35:00`
Duration	Elapsed or total execution time	`5m 0s`

Progress Timeline

Chronological log of task execution phases:

[HH:MM:SS] Event Type: Message

Event Types:

Started: Task began execution
Progress: Intermediate progress update
Completed: Task finished successfully
Error: Non-fatal error occurred
Failed: Task failed, execution stopped

Use: Track task progress, identify bottlenecks, debug failures

Results Section

For completed tasks, shows:

Files Changed: List of modified files with change counts
Summary: Agent's explanation of what was accomplished
Next Steps: Suggested actions for user

For failed tasks, shows:

Error Details: Specific error message
Troubleshooting: Steps to resolve the issue

Common Scenarios

Scenario 1: Monitoring Active Task

Check progress of currently running task:

vim

" Submit task
:LovelaceTask
" Description: Refactor module to TypeScript

" Task submitted (task_abc123) - Status: queued

" Check status
:LovelaceTaskStatus task_abc123

" View progress updates in real-time
" Updates appear automatically as task progresses

Expected behavior: Status updates every 5-15 seconds as task progresses

Scenario 2: Reviewing Completed Results

View results after task completes:

vim

" Task completion notification appears
" [Task abc123] Completed: 2 files changed

:LovelaceTaskStatus task_abc123

" Review file changes
" Read summary and next steps
" Close window when done

Expected behavior: Full results with file diffs and summary

Scenario 3: Debugging Failed Task

Investigate why task failed:

vim

" Task failure notification
" [Task abc123] Failed: Validation error

:LovelaceTaskStatus task_abc123

" Read error details
" Review progress timeline to see where it failed
" Check troubleshooting steps

Expected behavior: Error message with context and troubleshooting guidance

Scenario 4: Checking Queue Position

See where queued task is in line:

vim

:LovelaceTaskStatus task_abc123

" Output shows:
" ## Queue Position
" Position: 3 of 7

Expected behavior: Position in queue, estimated wait time

Advanced Usage

Continuous Monitoring

Monitor task progress with repeated checks:

vim

" Open task status
:LovelaceTaskStatus task_abc123

" Status buffer updates automatically
" No need to close and reopen

" Press 'q' when done monitoring

Auto-refresh: Status buffer refreshes every 5 seconds during execution

Programmatic Access

lua

local lovelace = require("lovelace")
local connection = lovelace.get_connection()

connection:call("task.status", {
  task_id = "task_abc123"
}, function(result, error)
  if result then
    print("Status: " .. result.status)
    print("Duration: " .. result.duration)

    if result.status == "completed" then
      print("Files changed: " .. #result.files_changed)
    elseif result.status == "failed" then
      print("Error: " .. result.error_message)
    end
  end
end)

Custom Status Display

lua

-- Create custom status display function
local function show_task_status(task_id)
  local lovelace = require("lovelace")
  local status = lovelace.get_task_status(task_id)

  if not status then
    vim.notify("Task not found: " .. task_id)
    return
  end

  -- Custom formatting
  local lines = {
    "Task: " .. task_id,
    "Status: " .. status.state,
    "Duration: " .. status.duration,
  }

  if status.state == "completed" then
    table.insert(lines, "✓ Success")
  elseif status.state == "failed" then
    table.insert(lines, "✗ " .. status.error)
  end

  -- Display in floating window
  local buf = vim.api.nvim_create_buf(false, true)
  vim.api.nvim_buf_set_lines(buf, 0, -1, false, lines)

  -- Create floating window
  local opts = {
    relative = "cursor",
    width = 50,
    height = #lines,
    row = 1,
    col = 0,
    style = "minimal",
    border = "rounded"
  }
  vim.api.nvim_open_win(buf, true, opts)
end

Troubleshooting

"Task not found" Error

Symptom: :LovelaceTaskStatus task_abc123 shows "Task not found"

Solutions:

Verify task ID:
vim
```
:LovelaceTasks
" Check if task_abc123 exists in list
```
Check task age:
- Tasks older than 24 hours may be archived
- Contact administrator for historical tasks
Verify connection:
vim
```
:LovelaceHealth
```

Status Not Updating

Symptom: Task status shows "Running" but no new progress updates

Solutions:

Check agent status:
vim
```
:LovelaceAgents
" Verify agent is still active
```
Check task timeout:
- Tasks have 10-minute timeout
- Long-running tasks may have timed out
Restart status view:
vim
```
" Close status window
q

" Reopen
:LovelaceTaskStatus task_abc123
```

Empty Results Section

Symptom: Completed task shows no results or file changes

Solutions:

Check task type:
- Some tasks (analysis, questions) produce text output, not file changes
- Results may be in summary only
Verify completion:
vim
```
:messages
" Check for completion notification
```
Check agent logs:
bash
```
localhost-ctl logs | grep task_abc123
```

Integration Patterns

Pre-Apply Workflow

Review task results before applying changes:

vim

" 1. Submit task
:LovelaceTask
" Description: Add types to user module

" 2. Wait for completion
" [Task abc123] Completed: 1 file changed

" 3. Review results
:LovelaceTaskStatus task_abc123

" 4. Read file changes section
" 5. Read summary
" 6. Check next steps

" 7. Apply changes if satisfied
" (Future feature: :LovelaceApply task_abc123)

Error Recovery Workflow

Diagnose and retry failed tasks:

vim

" 1. Task fails
" [Task abc123] Failed: Validation error

" 2. Check what went wrong
:LovelaceTaskStatus task_abc123

" 3. Read error details
" Error: Generated code contains syntax errors

" 4. Identify root cause
" Issue: Task description was ambiguous

" 5. Resubmit with clearer description
:LovelaceTask
" Description: Add TypeScript type annotations to User interface,
" including proper types for id (string), name (string), and
" createdAt (Date)

Batch Task Monitoring

Monitor multiple tasks:

vim

" Submit multiple tasks
:LovelaceTask  " Task 1
:LovelaceTask  " Task 2
:LovelaceTask  " Task 3

" List all tasks
:LovelaceTasks

" Check each task status
:LovelaceTaskStatus task_001
:LovelaceTaskStatus task_002
:LovelaceTaskStatus task_003

" Or create custom monitoring function (Lua)

Related Commands

Command	Purpose
:LovelaceTasks	List all tasks
:LovelaceTask	Submit new task
:LovelaceAgents	View agent worker status
:LovelaceCancel	Cancel running task

Next Steps

:LovelaceTasks - List all tasks across states
Task Monitoring Guide - Complete monitoring workflows
:LovelaceCancel - Cancel running tasks
Troubleshooting - Common task issues

Lovelace Developer Portal

:LovelaceTaskStatus

Command Signature

Description

Usage

Basic Usage

Get Task ID

From Lua

Output Format

Task State Details

Queued State

Running State

Completed State

Failed State

Information Fields

Task Metadata

Progress Timeline

Results Section

Common Scenarios

Scenario 1: Monitoring Active Task

Scenario 2: Reviewing Completed Results

Scenario 3: Debugging Failed Task

Scenario 4: Checking Queue Position

Advanced Usage

Continuous Monitoring

Programmatic Access

Custom Status Display

Troubleshooting

"Task not found" Error

Status Not Updating

Empty Results Section

Integration Patterns

Pre-Apply Workflow

Error Recovery Workflow

Batch Task Monitoring

Related Commands

Next Steps

Related Documentation

Lovelace Developer Portal