Skip to main content
Parley Agent is as useful for maintaining a workspace as it is for populating one.

​
Records, fields, and notes

The Agent can create, inspect, update, and organize Projects, Accounts, Contacts, and their first-class relationships. It can manage organization-defined resource fields and create, update, or bulk-import shared notes. It can also list existing Projects, Accounts, Contacts, files, and generated Project outputs. This makes it useful for audits and for confirming what already exists before changing anything.

​
File trees

Parley Agent manages the file trees owned by Projects, Accounts, Contacts, and the firm Library. It can:
  • Create folders
  • Upload source files
  • Move or rename existing files and folders
  • Read extracted text from processed documents for review and search
Moving or renaming an existing item preserves it in place. The Agent does not need to delete and re-upload hundreds of files merely to apply a new folder structure or naming convention.

​
Publishing Skills

Parley Agent can publish and maintain reusable Skills. When changing an existing Skill, it starts from a current copy, updates the instructions and reference materials, and publishes the reviewed version. A Skill publication mirrors the local Skill directory. Starting from the current version prevents newer reference materials from being removed accidentally when the revised Skill is published. See Skills for how Skills are written and used, and Practice areas for the library Parley ships with.

​
Guardrails

Before changing existing data, Parley Agent inspects the relevant records and searches for possible matches. If more than one record could be the intended match, it stops for clarification rather than guessing. Bulk creation, updates, and links require review of the scope and mapping before execution. Destructive cleanup, such as deleting records or files, requires separate and explicit confirmation. The Agent does not automatically merge or delete duplicate candidates. These guardrails make a bulk operation understandable before it starts, recoverable while it runs, and auditable after it finishes.