FieldCure.AssistStudio.Runner

FieldCure.AssistStudio.Runner

Windows-only headless LLM task automation engine — define natural language tasks, schedule them via Windows Task Scheduler (recurring or one-time), and get results delivered through Slack, Telegram, Email, KakaoTalk, or Discord. Runs as an MCP server for task management or standalone for headless execution.

Install

dotnet tool install -g FieldCure.AssistStudio.Runner

The published package is Windows-only because scheduling is implemented via Windows Task Scheduler and credentials are stored in Windows Credential Manager.

Quick Start

# Create runner.json config template
assiststudio-runner config init

# Set API key
assiststudio-runner config set-credential "Claude Sonnet" sk-ant-api03-...

# Start MCP server
assiststudio-runner serve

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "runner": {
      "command": "assiststudio-runner",
      "args": ["serve"]
    }
  }
}

Tools (7)

Tool	Description	Confirmation
create_task	Create a task with prompt, schedule, and MCP servers	Required
update_task	Modify task fields (partial update)	Required
delete_task	Delete a task and its history	Required
list_tasks	List all tasks with last execution status	—
run_task	Start task execution (async or wait up to 60s)	Required
get_task_history	Query execution history for a task	—
get_execution_status	Check status of a running execution	—

Execution Modes

Mode	Command	Purpose
Serve	assiststudio-runner serve	MCP server for task CRUD + execution
Exec	assiststudio-runner exec <task-id>	Headless single-task execution
Config	assiststudio-runner config <cmd>	Credential and configuration management

Requirements

• .NET 8.0 Runtime or later
• Windows (required for Task Scheduler and Credential Manager)
• FieldCure.Ai.Providers (bundled)
• FieldCure.Ai.Execution (bundled)

Scheduled tasks are registered with Windows Task Scheduler in interactive mode, so the user must be logged in when the trigger fires.

Designed for AssistStudio

Runner is purpose-built for the AssistStudio ecosystem. Tasks are typically created through natural language conversations in AssistStudio, which handles workflow design, MCP server selection, and tool permissions automatically.

While Runner can be used standalone with Claude Desktop or VS Code (via serve mode), you'll need to construct task parameters (prompt, MCP servers, allowed tools) manually. For the full experience, use AssistStudio.

See Also

Part of the AssistStudio ecosystem.

• GitHub
• MCP Specification