Skip to content
foxctl foxctl

Home

local control plane for agentic code work

foxctl

Local control plane for agentic code work.

Code retrieval, skills, memory, context, agents, rooms, and operational workflows under one inspectable CLI.

Start with foxctlBrowse docs
Start herefoxctl run code/semantic_search --input '{"format":"tree"}'
workflow preview
01OrientBuild a ranked map of the repo before changing code.
$ foxctl run code/semantic_search --input '{"format":"tree"}'
02RetrieveIndex symbols, imports, calls, references, and files.
$ foxctl index repo build --workspace . --go --typescript --elixir
03PlanPull the exact evidence needed for a bounded implementation path.
$ foxctl run code/dag_grep --input '{"query":"buildEvidencePack"}'
04ActCoordinate persistent agents and rooms when the work needs hands.
$ foxctl agent spawn --role reviewer --exec-mode autonomous
Progress

What is current, and what is still moving

The site separates shipped behavior from plan-backed work so agents can avoid treating experimental runtime and evaluation work as production operator guidance.

CurrentDocs and deploy path

Starlight site, Cloudflare Pages deploy script, docs checks, link checks, and production verification docs.

CurrentRepo evidence loop

Repoindex, semantic search, DAG grep, codemaps, and CAS-backed outputs are documented as operator workflows.

CurrentAgent and room operations

Agent lifecycle, orchestration, rooms, storage, and observability have current behavior docs.

In progressDurable execution recovery

Crash recovery, idempotent side effects, and effect journal work remain tied to active plans.

In progressRefactor intelligence

Hotspot detection, confidence scoring, target selection, and slop detection are being hardened.

In progressRLM and helper runtime

LongCoT evals, helper pipelines, recursive fanout, and smolvm runtime work are still experimental.

Read progress details
Integrations

Connectors that make foxctl useful in real workflows

Integrations are grouped by status: current surfaces are safe to build on, while runtime adapter work remains explicitly marked in progress.

CurrentProviders and MCP

LLM provider detection plus MCP serving for editor and agent tool access.

Open docs
CurrentOpenAPI and plugins

Generic OpenAPI calls, auth strategies, pagination, retries, CAS output, and plugin hooks.

Open docs
CurrentHooks

Session, tool, agent, and lifecycle events wired to structured actions and safety decisions.

Open docs
CurrentChat platforms

Discord, Telegram, and Teams adapters route commands and conversation into foxctl sessions.

Open docs
CurrentObsidian bridge

Vault indexing for notes, wikilinks, aliases, tags, and retrieval-oriented memory.

Open docs
In progressSandbox and runtime adapters

OpenSandbox, RLM, durable execution, and Go-native runtime plans are still plan-backed work.

Open docs
Ways to use it

A practical loop for agentic code work

foxctl makes the repeatable path explicit: orient the agent, retrieve grounded evidence, plan with context, act through tools, then verify the result.

01Orient

Build a ranked map of the repo before changing code.

02Retrieve

Index symbols, imports, calls, references, and files.

03Plan

Pull the exact evidence needed for a bounded implementation path.

04Act

Coordinate persistent agents and rooms when the work needs hands.

05Verify

Keep outputs reproducible, protocol-shaped, and CI-visible.

Main surfaces

The system pieces foxctl gives you

CLIcommands

A single entry point for repo search, skill runs, agent control, docs refresh, and local operations.

Read the guide
Retrievalrepoindex

Semantic search, graph navigation, DAG grep, snippet extraction, and codemaps for grounded context.

Read the guide
Skillsruntime

Job-tracked, ephemeral, and direct execution paths for installable tools with stable envelopes.

Read the guide
Agentsrooms

Persistent sessions, mailbox asks, overseer coordination, and durable room timelines.

Read the guide
Storageevidence

CAS, vectors, Turso, and Postgres keep large artifacts and working memory inspectable.

Read the guide
Benchmark solutions

Performance checks that protect real hot paths

Benchmarks are wired as a runnable solution, not a static report: the curated runner keeps repo search, storage, execution, and scan helper costs visible during local work.

bench:goCurated benchmark runner

A repeatable package set with count, time, pattern, and output capture controls.

Review
searchRepoindex query paths

Measures zero-result fallback, scored search, syntax fallback, and allocation cost.

Review
CAS + DBStorage hot paths

Covers CAS buffering, slice preallocation, cancellation checks, and row scan helpers.

Review
Architecture

Canonical storage, disposable context, durable evidence

Commands return envelopes, large artifacts go to CAS, repo metadata stays rebuildable, and agent work is anchored to durable room and session records.

CLIcommands, hooks, local shells
SkillsWASI, native, job tracking
Retrievalsemantic search, repoindex, codemaps
Agentsdaemon, rooms, overseer flow
StorageTurso, Postgres, CAS, vectors
Deep links
QuickstartIntegrationsProgressBenchmarksProtocol v1Repoindex