Any agent that can run terminal commands can use Wiele through the wiele CLI: Claude Code, Codex, Cursor's agent and others. The agent acts as the person whose session it uses. It sees what that person can see and can change what they can change. Agents don't count as members on your plan.
Agents without a shell, or clients that prefer remote tools, can use the MCP server instead.
Set up with one prompt
The quickstart prompt installs the CLI, signs you in, creates an organization and a workspace, and saves a first folder. Paste it into the agent's chat. The agent asks you for your email, the sign-in code and to add a card, and runs everything else.
Install the skills
The CLI ships four agent skills, Markdown instructions that teach an agent the safe way to use Wiele:
| Skill | What it covers |
|---|---|
wiele-setup |
Set up a new workspace for your goal: ask what it's for, propose a folder layout with a README, create it. |
wiele-workspace |
Find, fetch, read, edit and push files; handle stale heads, conflicts and payment errors; restore versions; retention. |
wiele-conflicts |
Review a merge plan and resolve whole-file conflicts against a pinned draft. |
wiele-sync |
Turn live uploads and download sync on and off without losing local work. |
wiele skills install writes them into a new folder as NAME/SKILL.md:
wiele skills install --directory /tmp/wiele-skills
The folder must not exist yet, so install into a fresh folder and move the skill folders to where your agent reads skills. For Claude Code, that's ~/.claude/skills for every project, or .claude/skills in one project:
mkdir -p ~/.claude/skills
mv /tmp/wiele-skills/wiele-* ~/.claude/skills/
For Codex, Cursor and other tools, use the folder their docs name for skills or rules. If a tool has no skills, print a skill and add it to the project's AGENTS.md or rules file:
wiele skills print wiele-workspace
The skills match the CLI version that wrote them. Install them again after you update the CLI.
Set up a workspace for a goal
Once the skills are installed, describe what the workspace is for and the wiele-setup skill does the rest:
"Set up a Wiele workspace for our podcast: show notes, guest research and the editing schedule."
The agent asks who works in it, what comes in and what goes out, then proposes a layout: a README.md that says what goes where, docs/ for what is true now, raw/ for material as it arrived, log/ for a dated work log, and a folder for what the project produces. It creates the workspace only after you agree, fills the starter files with what you told it and pushes them. The cookbook has worked layouts, such as social media.
Sign the agent in
If you can, sign in yourself in a terminal with wiele login before the agent starts. The agent then uses the saved session.
If the agent has to drive sign-in, it runs wiele auth start --email ADDRESS --json, asks you for the code, and pipes it into wiele auth verify --challenge ID --code-stdin. See Authentication.
Cloud sandboxes and containers usually have no keychain. Use a session file there:
mkdir -m 700 ~/.wiele
wiele login --credential-file ~/.wiele/session.json
Tips for agent runs
- Pass
--json --non-interactivewhen the agent reads results. Checkokand the exit code, and follownextActionson errors. - Small text files can be read and written without a checkout:
wiele read PATHandwiele write PATH --from FILE --if-sha256 HASH. Every write needs a precondition, so an agent can't overwrite a change it hasn't seen. - For larger work, fetch the folder, let the agent edit the files with its own tools, then
wiele status,wiele diffandwiele push -m "MESSAGE". - To search content, fetch the folder and search it locally with
rgorgrep. Server-side search is off. - Give an agent its own copy for bigger changes, so a person reviews and merges the result.
- Ask the agent to report the revision SHA after a push. A push isn't saved until the command reports a committed revision.
Example requests
Once the skills are installed, plain requests work:
- "Set up a workspace for the Q1 hiring round."
- "Put
~/projects/proposalin Wiele, in theclient-workworkspace." - "Fetch
client-work:/acmeand summarize what changed this week." - "Make a copy called
acme-rewrite, rewrite the proposal there, and show me the diff against main." - "Restore
budget.xlsxas it was before yesterday's push." - "Keep
~/Wiele/notesin sync while I work."