Skip to main content
Use one folder per organization. Run Deepline from inside that folder.

Setup

1. Create Folders

Create a predictable folder layout with separate input, output, and play files for each org.
Organize my workspace into one folder for each organization.
Put the right data and assets in each folder.

2. Set Orgs

Run the folder-scoped org command inside every org folder.
Set the Deepline org for each folder using deepline org -h.
Verify the saved .env.deepline path is inside each folder.
Final state:
~/deepline/
  workspaces/
    acme/
      .env.deepline  # Acme workspace-specific API key
      input/
        leads.csv
      output/
      plays/
    globex/
      .env.deepline  # Globex workspace-specific API key
      input/
        leads.csv
      output/
      plays/
The CLI creates .env.deepline; you normally should not write it by hand. If org status points at a parent folder’s .env.deepline, remove that parent pin or rerun from the intended org folder after clearing it.

3. Run Agents From Folders

Start agents from inside the right org folder for foolproof org usage. You can also start from ~/deepline, but tell the agent to cd into the right workspace folder before it runs deepline.
Run Deepline from within each folder so the right org API key is used.
Check the org before running workflows.

Audit folder bindings

Check which org each folder is bound to.
Report org status for each folder in my workspace.

Fix the wrong org

Change only the folder that is wrong, then verify it.
This folder should use <ORG_NAME>.
Check the current org, fix only this folder, then verify it.

Reference

Run deepline org -h for the current org commands and auth-scope behavior.