Skip to main content
Parley CLI is the command-line interface to your workspace. It manages Projects, Accounts, Contacts, their links, files, notes, resource fields, and reusable Skills in a controlled, repeatable way. It’s for work that’s too large or too repetitive for chat — importing a historical client list, normalizing records after a migration, or applying the same Project structure across many matters.

​
What it doesn’t do

The CLI is not a replacement for Parley’s drafting agents. It prepares and organizes the underlying records and source files, and it can list work product already generated for a Project. It does not generate, open, or download drafts, forms, briefs, or packets. If the task is producing a work product, that’s the Agent. If the task is getting the records and files into the right shape so the Agent can do that well, that’s the CLI.

​
When to use it

Most firms use the Agent for ordinary, one-off work. Reach for the CLI when you need a process that is repeatable, reviewable, and driven by a file you control:
  • Importing Accounts and Contacts from a clean CSV
  • Creating or updating a defined set of resource-field values
  • Linking existing records at scale
  • Organizing a file tree
  • Publishing or maintaining a reusable Skill
For a spreadsheet migration, use the dedicated import workflow rather than running one create command per row. The importer validates a prepared CSV, processes it in one long-lived run, retains a progress log, and supports safe recovery after an interruption. See Importing data.

​
The batch pattern

Bulk imports use a match-or-create model, and understanding it is the difference between an import you can trust and one you have to unpick. You select a stable natural key in the source data — an Account name, or another genuinely unique field — and the importer resolves each row against the records visible to you in Parley. A matching record is retained. A missing record is created. For Accounts, Contacts, and Projects, nonblank source values can also update the matched record when they differ from what Parley currently stores. Blank cells are skipped; they do not clear existing values. Links are resolved separately from the matching key. Import Accounts first, then import Contacts and link each Contact to the appropriate Account.
This is what makes an import safe to rerun — as long as the source data, matching key, and progress log are preserved. A failed or interrupted batch can be corrected and resumed without blindly recreating records that were already created or matched.

​
Where to go next

Importing data

Prepare CSVs, dry run, import Accounts then Contacts, and recover from an interrupted run.

Workspace maintenance

Records, fields, notes, file trees, Skills, and read-only lookups.

Guardrails

The practices that keep a bulk operation reviewable and reversible.