Ferryman is a local-first desktop AI workspace built around Sessions, Skills, Tasks, Artifacts, Runtime Logs, Model Management, and Model Routing.
Private preview for teams that need dependable automation, not another chat box.
Every run leaves a trail: context lives in Sessions, execution appears in Tasks and Runtime Logs, outputs land in Artifacts, and model choices stay visible.
Each project keeps its own context, history, and working memory instead of dissolving into one endless chat.
Execution is broken into visible tasks so you can see what is running, waiting, finished, or blocked.
A Skill is an operational playbook: SOP, tool scope, working assumptions, and output shape bundled into one reusable unit.
Ferryman writes outputs to disk so the result is a usable file, not just text that disappears in chat history.
When something breaks, the trail is still there. Logs turn debugging from guesswork into diagnosis.
Providers, keys, base URLs, and active models stay in your control instead of being hidden behind one vendor opinion.
Different work deserves different engines. Ferryman can route planning, execution, and formatting to the model path that fits the job.
Ferryman is not trying to look magical. It is designed to stay legible when execution, credentials, files, and failure states matter.
Keep tasks, outputs, provider settings, and browser work close to the operator instead of pushing everything into a remote black box.
Sessions, task state, token usage, runtime logs, and saved artifacts make the system understandable while it works.
Bring your own providers, choose the active model, and route different stages of work through the model path that makes sense.
Ferryman is designed for real browser work, so the system can surface checkpoints instead of pretending every edge case should be automated away.
Each Skill packages process, tools, assumptions, and output shape so the same intent can be executed repeatedly without turning into vague chat instructions.
A Skill defines what good execution looks like before a model starts improvising. That means scope, steps, constraints, and expected deliverables are already shaped.
A Skill is tied to concrete tool access and expected outputs. It can read files, drive the browser, write artifacts, and carry local context without pretending the world is just text.
The result is a durable working surface, not a one-off answer.
Ferryman is opinionated about execution so your workflows stay reusable.
Requests do not float in isolation. Sessions preserve history, task state, and the working surface for a given stream of work.
Ferryman decides which Skill, which tool surface, and which model path should carry the request forward.
Browser actions, file writes, task updates, and runtime logs remain inspectable while the system is moving.
The end state is a saved output you can inspect, hand off, version, or reuse, not a transient answer lost in scrollback.
Ferryman is currently available by private preview.