Choose a workspace for each project

1. Have your context ready

Know which workspace belongs to each folder and ensure your account has access to it.

2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

/deepline-gtm Check the Deepline workspace currently used by this folder. Show me the workspace identity and whether the folder has its own binding. I want this folder to use the workspace I identify next. Explain the binding change before applying it, then verify the effective workspace from the same folder. Do not switch unrelated folders or run provider work.

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

3. Review the result

Each folder resolves to its intended workspace. An authorized account can still be bound to the wrong workspace for this project. Ask your agent:

/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.

Approve a larger job, recurring work, or external changes only after reviewing that decision.

Check your understanding

Two projects share a default workspace. Is changing that default enough to keep their work separate?

Show the answer

No. Ask the agent to bind and verify the intended workspace for each project folder.

Background Agents

​1. Have your context ready

​2. Ask your agent

​3. Review the result

​Check your understanding

​Related guides

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

Related guides