Script Your Workspace: The idapt CLI
Everything in your idapt workspace has a command: chats, Drive files, agents, memory, computers, secrets, generation. The CLI makes the workspace scriptable, which is where repeated work wants to live.
Setup, once
Install from the CLI page, then authenticate. Discovery is built in and lazy: idapt help <resource> <verb> shows a command's exact arguments, and idapt instructions <resource> prints the playbook for a resource. You never memorize the surface; you ask it.
Five recipes to steal
1. Ask from anywhere
idapt chat send --new "Summarize this error and suggest a fix: $(tail -50 app.log)"
2. Ship a file to Drive from CI
idapt drive upload ./dist/report.pdf --folder "Reports/$(date +%Y-%m)"
3. Give an agent a task
idapt agent run research-agent "Compare the top 3 vector databases for our stack; write findings to /Research"
4. Query shared memory
idapt memory recall research-agent "what did we decide about pgvector"
5. Generate an image in a pipeline
idapt image generate "isometric server room, blueprint style" --model flux-schnell --out ./assets/hero.png
Where the CLI earns its keep
Cron jobs and CI are the obvious homes: the Monday automation pattern works from your own scheduler too. Less obvious: the CLI is how agents on your machines reach the workspace, so a script and an agent share the same verbs, memory, and Drive: one contract, every surface.
Good to know
- Auth supports scoped API keys; a CI key can be limited to exactly the verbs it needs.
- Output is script-friendly; add
--jsonwhere you want to parse. - The same command surface is exposed to external tools over MCP and to code via the SDK.
Start with recipe 1 aliased in your shell; the CLI help articles cover installation, commands, and scripting patterns in depth.
Found this helpful? Share it: