Skip to main content
Human guide: work with your agent → Bind one working folder to one Deepline workspace. Verify the binding before using customer inputs or starting provider work.

​
1. Create a dedicated folder

Keep that workspace’s files inside its folder. Create a separate folder when you need another workspace.

​
2. Select an accessible workspace

Replace Acme with an accessible workspace returned by the list. The CLI saves the folder binding. Do not construct .env.deepline manually.

​
3. Verify the effective binding

Check the reported workspace and credential source. A parent’s folder binding or inherited credential can differ from your intended selection.
The effective workspace matches the folder’s purpose. Its reported folder binding points to the intended project, not another customer’s directory.

​
4. Repeat in the next folder

Create a sibling folder for the next workspace. Run org set from inside it with --auth-scope folder. Verify status there before running a Play. Tell unattended agents to enter their assigned folder before calling Deepline. Use Background agents for run identity and recovery.

​
Fix a mismatch

Stop provider work while the effective workspace is wrong. Return to the intended folder and set its binding again. Read the status output afterward. If the CLI reports an ambiguous project folder, resolve that ambiguity first. Do not delete a parent’s binding without understanding which other projects use it. Ask your agent to explain credential provenance from status output. Use deepline org --help for the current scope contract.