FOXORA / DOCUMENTATION
Foxora StudioA little guidance. A lot you can do.
Choose a short path through Studio and finish one real task before opening the deeper reference library.
TutorialsTutorials
TutorialsStart here
Choose a short path through Studio and finish one real task before opening the deeper reference library.
02Install and sign in
Install Foxora Studio, sign in in your browser, and finish the four first-run choices.
03Complete your first task
Describe one outcome, send it, and verify the result in the task transcript.
04Add a project or file
Give Foxora only the folder, file, image, or browser tab needed for the task.
Documentation
36 / DocumentationTutorials
Choose a short path through Studio and finish one real task before opening the deeper reference library.
11 guides02Getting Started
Getting started means choosing where work runs, giving Fennec the right context, and verifying the result in the same task.
8 guides03Foxora Workspace
The workspace keeps tasks, projects, files, and supporting tools connected around the outcome you are currently pursuing.
6 guides04Tasks
A Foxora task is a persistent record of one outcome, including messages, tool activity, approvals, artifacts, status, and final results.
7 guides05Projects
Projects connect tasks to durable files, project instructions, environment settings, indexing, and optional Git information.
7 guides06Web App & Cloud
Foxora Web provides tasks, cloud files, Git projects, a real workspace terminal, and downloadable artifacts without installing Desktop.
7 guides07Task Composer
The task composer combines intent, autonomy, Fennec selection, project context, attachments, voice, and the request you send.
8 guides08Autonomy & Approvals
Autonomy controls when Foxora asks before a mutating action; it does not change read-only access, model quality, or hard safety policy.
8 guides09The Stage
Stage is Foxora’s right-side workspace for terminals, previews, files, artifacts, media, background tasks, and other supporting surfaces.
6 guides10Terminal
Terminal in the full Desktop or Web runtime is a real interactive shell rooted in the selected project or managed cloud workspace.
6 guides11Files & Editor
Files and Editor provide a project-aware tree, tabs, direct editing, Git-aware review, and links back to the task that produced a change.
6 guides12Source Control
Foxora displays branch and change status, but current Git staging, commits, and conflict work are performed through Terminal or an explicit task.
6 guides13Browser
Browser tasks navigate, read, click, fill, and capture evidence through the task transcript; Stage Preview is a separate surface for app previews.
7 guides14Computer Use
Computer Use lets Foxora interact with supported desktop applications when browser, file, or command tools cannot complete the visible workflow directly.
6 guides15Agents
Agents are reusable specialists. Fennec remains the coordinator and can delegate to an eligible agent when its role fits the task.
8 guides16Crews
A crew is a supervised team. Fennec coordinates compatible agents, verifies their work, and reports one result.
7 guides17Bots
Studio no longer has a separate Bots library. Customer-facing chat is built from a Bot agent inside a Chatbot crew.
7 guides18Skills
Skills are reusable Runtime playbooks that an agent can load when relevant. The current managed catalog is read-only in Studio, so it presents published identity and capability information without exposing the full playbook or scripts.
7 guides19Tools
Tools are executable capabilities discovered from the workspace, MCP servers, and connected apps. The Studio catalog is intentionally read-only.
7 guides20Memory Den
Memory Den is a read-only view of the Runtime’s canonical cognitive state across conversations, observations, active context, and durable knowledge.
7 guides21Scheduled Tasks
Schedules are time-based automations and recurring workflow runs. They are authored through the task composer and workflow canvas, not as a separate editable task record.
7 guides22Workflows
Workflows automate schedules or connected-app events by chaining agent, tool, condition, delay, approval, loop, and notification steps.
8 guides23Runs
Runs combines live tasks, specialists, commands, workflow executions, and durable history in one read-only operational view.
7 guides24Plugins
Plugins connect external apps through Foxora’s gateway and add their available actions to Studio.
7 guides25Channels
Channels bring Fennec into messaging, email, event, and voice services while Foxora hosts the connection runtime. Each installation combines provider credentials, a compatible crew, and channel-specific access rules.
6 guides26MCP
Foxora uses MCP in two distinct directions: connected plugins can supply tools to Fennec, while Foxora can expose a small read-only tool set to external MCP clients.
7 guides27Models
Foxora separates the Fennec experience from provider model names. Managed Fennec tiers route through the Foxora AI Gateway, while optional provider connections let custom agents use your own model accounts.
7 guides28Settings
Settings contains account-wide and device-specific controls for Foxora. Agent, crew, workflow, and task behavior still belongs in the builder or surface that owns it.
10 guides29Account & Authentication
Use one Foxora account across Studio, the account dashboard, and the CLI while keeping device-local work separate from account access.
8 guides30Plans, Credits & Usage
Use the live account dashboard to compare plans, track Foxora credits, and manage billing without relying on static limits or prices.
8 guides31Security & Privacy
Secure Foxora by separating account access, task authority, connected services, and device-local data instead of treating them as one permission.
7 guides32Foxora CLI
Use the Foxora CLI for interactive terminal work or one-shot runs backed by the same account and device runtime as Studio.
8 guides33API Reference
Use https://api.foxora.ai for the current /v1 account, discovery, usage, and OpenAI-compatible chat-completions routes.
8 guides34Troubleshooting
Troubleshoot Foxora by identifying the failing surface, preserving the exact error, and changing one layer at a time.
10 guides35FAQ
Use this FAQ for quick product boundaries, then follow the linked section when you need exact steps or a current account value.
6 guides36Release Notes
Use release notes with the installed client version to understand changes, plan an update, and verify the result.
6 guides