Run a task end to end
This walks the whole path once: configure a provider, hand an agent a task that touches files, and find the result. It assumes M.A.V.E.N is installed and running.
1. Configure one provider
Section titled “1. Configure one provider”Open Settings → Secrets and add the key for a provider you have - or, for an
agentic task, install a CLI: Claude Code (claude), Codex, Grok or Qwen Code. Claude
is the default. A key is written to .env.local and applied at once.
The provider’s sidebar dot turns from “needs a key” to available. If it does not, confirm the key and that the app was restarted (env files are read at startup).
2. Give the agent a task
Section titled “2. Give the agent a task”Open Chat, pick the engine in the row (say Claude), and in Settings set a
Working dir. Give it something concrete that writes a file - for
example, “create notes/threshold.md and write three sentences about control
planes”. The agent works in its own directory, takes a few steps, and reports what it
did.
3. Find the output
Section titled “3. Find the output”An agent writes to its working directory, which defaults to your home directory
(~) unless the app that launched it set one - so a file like notes/threshold.md
lands at ~/notes/threshold.md. App-generated artifacts (courses, decks, flipbooks,
media) are different: those go into the Obsidian vault (~/Obsidian/maven-os/, each
app in its own subfolder), and the console transcript appends to
~/Obsidian/maven-os/Memories/.
4. Make it the default engine
Section titled “4. Make it the default engine”If you want the default-engine apps (Loop, Pipeline) to use this provider, set it as the global model in the sidebar box. The choice persists across restarts.
What you just used
Section titled “What you just used”- The control plane routed your request.
- An agent - tools plus a working directory - did the work.
- Local-first: nothing left your machine except the call to the provider whose key you supplied.