Join the open beta
The Docusign CLI open beta gives developers early access to a tool for implementing Docusign Agreement Manager programmatically. During the beta, you can explore the full set of CLI features, build and test implementations against real agreements, and share feedback that shapes how the CLI evolves.
The beta is open to all developers with a Docusign developer account. There are no restrictions on usage, and no approval process to complete before getting started.
Benefits of participating
Joining the open beta gives you the opportunity to influence the direction of the Docusign CLI before it reaches general availability.
Additional benefits of participating include:
- Early access to new features. Get hands-on experience with CLI capabilities before they are broadly released.
- A head start on implementation. Begin building and validating Agreement Manager configurations now, reducing time-to-value when the CLI reaches general availability.
How to get started
See Get started with the Docusign CLI for the setup process, including prerequisites, installation, and configuration.
Share your feedback
Feedback from beta participants is essential to improving the CLI. After using it, share your experience using the feedback form. The Docusign team reviews all submissions and uses them to guide future development.
The team is especially interested in hearing about:
- Features that work well
- Issues that you encounter while using the CLI
- Suggestions for additional capabilities that would make the CLI more valuable
Frequently asked questions
Do I need to request access to join the open beta?
No. The open beta is available without any access request or approval process. Install the CLI and start using it immediately. All developer accounts have access to Agreement Manager.
What do I need to get started?
You need a Docusign developer account, as well as Node.js and npm installed on your machine. Mac users can install Node.js via Homebrew; Windows users can use the Node installer or other supported methods.
Is the CLI stable enough to use for real implementations during the beta?
Yes. Start by customizing and testing in your developer (demo) account, validate Agreement Manager’s accuracy there, and only then deploy the configurations to production.
How do I report a bug or request a feature?
Use the feedback form to report bugs, share feature requests, or describe friction you have encountered. The Docusign team reviews all submissions and uses them to prioritize fixes and improvements for upcoming releases.
Will my beta configurations be compatible with the general availability release?
The Docusign team aims to maintain compatibility between beta and general availability releases. To reduce the risk of changes affecting your implementation, be sure to upgrade the CLI whenever a new version is available.
Can I remove custom agreement types and fields from production?
No, custom agreement types and fields cannot be removed from an account. For this reason, make your customizations in the developer (demo) environment and test before deploying your configuration to production.
Next steps
- Install and configure the Docusign CLI.
- Explore common CLI use cases.
- Implement custom configurations easily with our AI tools.