Install & log in
edisyl runs in your own environment, so after installing the CLI you point it at your install’s API host and log in. Your edisyl admin has the host, usually https://api.<your-domain>.
-
Install the CLI.
Terminal window curl -fsSL https://cli.edisyl.com/install.sh | shIn PowerShell:
Terminal window irm https://cli.edisyl.com/install.ps1 | iexThis installs
edisyl.exeto%LOCALAPPDATA%\Programs\edisyland adds it to your userPATH. Terminals that were already open need a restart to pick up the newPATH. -
Point the CLI at your edisyl and log in.
Terminal window edisyl profile create work --endpoint https://api.<your-domain> --useedisyl login --profile workThe first command saves your API host as a profile and makes it active. The second opens your browser to sign in, then saves the session for future commands.
-
Confirm who and where you are.
Terminal window edisyl whoamiThis prints your user and workspace. The workspace (org) is already provisioned: you’re joining it, not creating it.
Run
edisyl helpto see the main commands, oredisyl <command> --helpfor any one of them.
Using a coding agent?
Section titled “Using a coding agent?”Run edisyl onboard and give your agent the output. It prints a self-contained guide to driving edisyl from the CLI: connecting a data source, teaching a pack, asking it questions, and tasking it with work. It needs no login and works offline.
Switch environments
Section titled “Switch environments”There are two ways to switch:
- Log out and log back in. Run
edisyl logout, thenedisyl loginand sign in with a different organization. This is simplest when you only move between them occasionally. - Create a profile for each environment. A profile stores an endpoint, its sign-in session, and the selected org under one name. You can switch profiles without signing in again.
To add a profile for another environment, such as a staging install, create it the same way as above and log in to that profile. Order matters: a bare edisyl login authenticates default, not work.
Three ways to select a profile, highest priority first:
| Selector | Use when |
|---|---|
--profile <name> / -p <name> |
One-off override on a single command |
EDISYL_PROFILE=<name> |
Persistent for a shell session or in CI |
edisyl profile use <name> |
Change the default for all future commands |
Tip: capture ids from any command with -j | jq -r '.id'. Every command supports -j/--json.
Next: Connect a data source.
Was this page helpful?
Thanks for the feedback.
