Inspect the Current Workspace Context
Check who the current principal is, which workspace is active, and which installation context is in effect before you run sensitive automation or admin work.
CLI In this interface
4 steps Steps
2 interfaces Available in
Use this path when
Use the CLI discovery commands plus status output before you do anything destructive or admin-scoped.
What you'll finish here
- Identify the current principal.
- Confirm the active workspace.
- Prevent admin work in the wrong workspace.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Do the work
- 1. Run `./backlog.sh status` to see the current profile, token source, and stored workspace id.
- 2. Run `./backlog.sh me` to confirm the principal type and current workspace context.
- 3. Run `./backlog.sh workspaces` if you need the workspace id for automation admin commands.
- 4. Persist the correct workspace id with `./backlog.sh config set-workspace <workspaceId>` before you continue.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.
CLI CLI Setup
Check CLI Status
Inspect the active CLI profile, token source, and workspace defaults before you run commands.
4 steps
CLI Automation and Agents
Create an Automation
Create the workspace automation boundary, issue the automation secret, and store that secret safely because it is only shown once.
4 steps