Workspace, find and publish
Use your Dexto workspace as yourself: tools, apps, search, publishing, your profile and skills.workspace
Section titled “workspace”dexto workspace uses your Dexto workspace as you: your connectors, Drive, Sites and Apps, Loops and
memory. They are the tools the Dexto MCP gives a chat, called from the
terminal. It needs your own sign-in. An API key cannot use it, and fails with exit 3.
These commands follow the output contract: JSON when stdout is not a terminal, failures as JSON on stderr, and exit codes 0 to 6.
dexto workspace # the apps your sign-in reachesdexto workspace <app> # one app's operationsdexto workspace <app> <operation> --help # the input it takesdexto workspace <app> <operation> --field value # run itAn operation takes its input as --field value, as --data '{"…":…}' for a JSON object, or as
--<field>-file path to read a value from a file (or - for stdin). Operations that take a file also
accept a local path or a link.
Operations have a level. Those that act for you, need your approval, or spend money ask first: they
exit 4 until you pass --yes. Ask your person, then repeat the command with --yes. Running an
operation with --help shows its level.
A permission your sign-in lacks exits 3, and fix is the dexto login --scope … command that grants it.
The same operations are available by tool name:
dexto workspace tools --search drive # list tools, optionally filtereddexto workspace describe dexto_search # a tool's description and input schemadexto workspace call dexto_search --data '{"query":"invoices"}'call takes a JSON object with --data or --file, and --yes for a tool that asks first.
Find, publish, profile and skills
Section titled “Find, publish, profile and skills”Generated from dexto 2.0.0-beta.0.
dexto find
Find what to run for something you want to do: Dexto's operations, apps, skills, agents and more, each as a command.
dexto find <what...> | Option | What it does |
|---|---|
--limit <limit> | How many to show (default 5, up to 8). |
JSON when stdout is not a terminal, failures as JSON on stderr, exit codes 0 to 6. Also takes the shared options below.
dexto publish
Publish a file, a folder or a .zip of one as a link anyone with it can open; publishing the same name again updates it.
dexto publish <path> | Option | What it does |
|---|---|
--name <name> | What it's called: the page's title and, with your handle, its address (default: the file or folder's name). Publishing the same name again updates the same link. |
--slug <slug> | Publish at <slug>.dexto.dev instead of an address made from the name; a Site of yours there is updated. |
--title <title> | The page's title (default: the name). |
--yes | Go ahead without being asked. Pass it only once your person has agreed. |
JSON when stdout is not a terminal, failures as JSON on stderr, exit codes 0 to 6. Also takes the shared options below.
dexto profile get
Show your Dexto profile: handle, name, bio, links, work and whether it is public.
dexto profile get JSON when stdout is not a terminal, failures as JSON on stderr, exit codes 0 to 6. Also takes the shared options below.
dexto profile update
Change your Dexto profile: only the fields you pass change, such as --handle shaun --visibility public.
dexto profile update | Option | What it does |
|---|---|
--bio <bio> | Your bio; "" clears it. |
--display-name <display-name> | Your display name. |
--handle <handle> | Your handle, unique across Dexto: 3 to 30 lowercase letters, digits and hyphens. |
--links <links> | Your links, replacing them all, as JSON: [{"kind":"github","url":"https://…"}] or {"kind":"custom","label":"…","url":"…"} entries. |
--token-usage <token-usage> | Whether your profile shows your token usage: show or hide. |
--visibility <visibility> | private, or public for anyone with the link. |
--work <work> | Your work entries, replacing them all, as JSON: {"kind":"site","siteId":"…"} or {"kind":"external","title":"…","url":"…","description":null,"imageUrl":null} entries. |
JSON when stdout is not a terminal, failures as JSON on stderr, exit codes 0 to 6. Also takes the shared options below.
dexto skills push
Pack a local Skill folder (SKILL.md at its root, dotfiles left out) and create or update it in your library.
dexto skills push <folder> | Option | What it does |
|---|---|
--description <description> | What the Skill does (default: description in SKILL.md's header). |
--slug <slug> | The Skill's slug (default: slug or name in SKILL.md's header, else the folder's name). |
--title <title> | The Skill's title (default: title in SKILL.md's header, else from the slug). |
--update | Update your Skill with this slug (default: update it if you have one, else create it). |
--yes | Go ahead without being asked. Pass it only once your person has agreed. |
JSON when stdout is not a terminal, failures as JSON on stderr, exit codes 0 to 6. Also takes the shared options below.
Shared options
Commands on this page that follow the JSON contract take these.
| Option | What it does |
|---|---|
--api-base-url <api-base-url> | The API origin (default https://api.dexto.ai, or DEXTO_API_BASE_URL). |
--api-key <api-key> | Use this key instead of DEXTO_API_KEY or the saved sign-in. |
--profile <profile> | The saved sign-in to use for this run (or DEXTO_PROFILE); see dexto accounts list. |
--project <project> | The Cloud project to act in when you're signed in (or DEXTO_CLOUD_PROJECT). |
--json | Print JSON, failures included (on stderr). The default when stdout isn't a terminal. |
--table | Print tables for people even when stdout isn't a terminal. |