# Quickstart This guide is for humans and operators who want DidaCLI installed, verified, authenticated, and ready for daily task automation. ## Install Unix-like systems: ```bash curl -fsSL https://raw.githubusercontent.com/DeliciousBuding/dida-cli/main/install.sh | sh ``` Windows PowerShell: ```powershell iwr https://raw.githubusercontent.com/DeliciousBuding/dida-cli/main/install.ps1 -UseB | iex ``` Optional environment variables: | Variable | Purpose | | --- | --- | | `DIDA_VERSION` | Install a specific release tag, for example `vX.Y.Z`. | | `DIDA_INSTALL_DIR` | Override the install directory. | | `DIDA_REPO` | Override the GitHub repository, for example for forks. | ## Verify ```bash dida version dida doctor --json ``` `doctor --json` is local-only by default. After login, use `--verify` for a read-only Web API health check: ```bash dida doctor --verify --json ``` ## Web API Login The Web API channel uses the browser session cookie captured locally. Manual flow (works everywhere): ```bash # Open dida365.com in your browser, sign in, then: dida auth cookie set --token-stdin --json # Paste the cookie named "t" when prompted. dida doctor --verify --json dida auth status --verify --json ``` Automated flow (requires Python): ```bash dida auth login --browser --json dida doctor --verify --json ``` Do not paste cookies into chat or issue trackers. Manual cookie import, when needed, should use stdin: ```bash dida auth cookie set --token-stdin ``` ## Agent First Read ```bash dida agent context --json dida agent context --outline --json ``` This gives agents a compact account context: projects, folders, tags, filters, today, upcoming, and quadrants. Use `--outline` for a lower-token variant with task id references and a deduplicated `taskIndex`. ## Schema Discovery ```bash dida schema list --compact --json dida schema list --json dida schema show task.create --json dida schema show openapi.login --json dida channel list --json ``` Inspect compact schema before generated writes. It tells agents which commands support `--dry-run`, `--yes`, and compact output. Use `schema show` for full command details, or full `schema list --json` when you need the complete local index with HTTP surfaces and notes. ## Official MCP Official MCP is the token-based official channel. It is separate from Web API cookie auth. ```bash DIDA365_TOKEN=... dida official doctor --json dida official token set --token-stdin --json dida official token status --json dida official tools --limit 20 --json dida official project list --json dida official project data --json dida official task query --query today --json dida official task filter --project --status 0 --json dida official task batch-add --args-json '{"tasks":[{"title":"Task"}]}' --dry-run --json ``` ## Official OpenAPI Official OpenAPI is OAuth-based REST. It is separate from Web API and official MCP. ```bash dida openapi doctor --json dida openapi client set --id --secret-stdin --json dida openapi login --browser --json dida openapi project list --json dida openapi project create --args-json '{"name":"Project","viewMode":"list","kind":"TASK"}' --dry-run --json dida openapi focus list --from 2026-04-01T00:00:00+0800 --to 2026-04-02T00:00:00+0800 --type 1 --json dida openapi habit list --json dida openapi habit checkin --args-json '{"stamp":20260407,"value":1}' --dry-run --json ``` Before `dida openapi login --browser --json`, configure the developer app OAuth redirect URL to the `default_redirect_uri` reported by `dida openapi doctor --json`. `dida openapi login --browser --json` opens the browser and emits one final JSON envelope after the OAuth callback. For manual no-browser flows, use `dida openapi auth-url --json` and `dida openapi listen-callback --json`. You may also use `DIDA365_OPENAPI_CLIENT_ID` and `DIDA365_OPENAPI_CLIENT_SECRET`; environment variables take precedence over the saved client config. For the full operator setup path, including where to register the redirect URL and how to run the manual callback flow, see [openapi-setup.md](openapi-setup.md). ## Common Reads ```bash dida project list --json dida task today --compact --json dida task upcoming --days 14 --limit 50 --compact --json dida task search --query "paper" --limit 20 --compact --json dida completed today --compact --json dida trash list --cursor 20 --compact --json dida stats general --json ``` ## Common Writes Preview generated writes first: ```bash dida task create --project --title "Read paper" --dry-run --json dida task update --project --title "Read paper carefully" --dry-run --json ``` Execute after the preview is correct: ```bash dida task create --project --title "Read paper" --json dida task complete --project --json ``` Destructive operations require `--yes`: ```bash dida task delete --project --dry-run --json dida task delete --project --yes --json ``` ## Agent Note This section is optimized for LLM/Agent operators. Prefer JSON commands, inspect `dida schema list --compact --json` before writes, preview generated writes with `--dry-run`, and never ask the user to paste cookies or tokens into chat.