foxctl Daemon

Route agent execution to LLMChatEngine behaviors by exec_mode.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-daemon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl Daemon
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills/foxctl-daemon
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-daemon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand and control how foxctl’s agent daemon selects execution engines so reactive agents respond correctly and autonomous/proactive agents can run tool-calling loops reliably.

Core Features & Use Cases

  • Engine Routing by exec_mode: Dispatches to the appropriate LLMChatEngine behavior for reactive, autonomous, and proactive modes using an internal companion service.
  • LLM Engine & Provider Selection: Configures provider defaults (e.g., cerebras fallback) and model selection to match each agent’s intent.
  • Autonomous vs Proactive Behavior: Maps mailbox-polling “wait for work” agents versus self-initiating background/scheduled agents to the right operational mode.
  • Operational Controls for Sessions: Supports context budget enforcement (e.g., stopping with StopReasonContextBudget) and session continuation by persisting turns and linking sessions.

Quick Start

Spawn an autonomous agent that self-runs with tool calling by executing: foxctl agent spawn --name "Coder" --role coder --exec-mode autonomous.

Frequently Asked Questions about foxctl Daemon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route agent execution modes for reactive versus autonomous agents?

Agent execution mode routing dispatches reactive, autonomous, and proactive behaviors to the correct LLMChatEngine using deterministic exec_mode selection. This ensures reactive agents respond to events while autonomous agents run continuous tool-calling loops reliably.

What is the difference between autonomous and proactive agent execution?

Autonomous agents operate via mailbox polling to wait for work, while proactive agents self-initiate background or scheduled tasks. Both map to distinct operational modes that determine how the LLM engine manages tool-calling loops and multi-step reasoning.

How do I enforce context budget limits during multi-step agent reasoning?

Context budget limits are enforced using max-context-tokens configuration, which triggers stop reasons like StopReasonContextBudget. This halts agent execution when token limits are reached, ensuring sessions stay within defined operational boundaries.

Can I configure provider fallbacks for LLM engine selection in agent daemons?

Provider defaults like cerebras fallback can be configured for LLM engine selection in agent daemons. Model selection matches each agent's intent, ensuring the correct provider resolves based on the defined execution mode and operational requirements.

How do I spawn an autonomous agent with tool calling capabilities?

Spawn an autonomous agent with tool calling by executing foxctl agent spawn with the name, role, and exec-mode set to autonomous. This initializes the agent to self-run tool-calling loops using the routed LLMChatEngine behavior.

Why does session continuity matter for autonomous agent orchestration?

Session continuity persists agent turns and links sessions to maintain context across multi-step reasoning loops. This allows autonomous and proactive agents to resume execution reliably without losing prior tool-calling state or operational context.