BUG: workspace status points to a workspace select <name> command that doesn't exist #7

New Issue

2026-02-16T04:15:07-05:00

yindo commented

2026-02-16 04:15:07 -05:00

Originally created by @gwtaylor on GitHub (Sep 25, 2025).

Thank you for releasing this useful suite of tools!

When running workspace status with no active workspace the help gives:

workspace status
Error: No active workspace

Caused by:
    No active workspace. Run: workspace select <name>

Running workspace select shows that is an unrecognized subcommand:

workspace status
Error: No active workspace

Caused by:
    No active workspace. Run: workspace select <name>

The help should point to the actual way to activate a workspace: export SEMTOOLS_WORKSPACE=<name>

Originally created by @gwtaylor on GitHub (Sep 25, 2025). Thank you for releasing this useful suite of tools! When running `workspace status` with no active workspace the help gives: ```bash workspace status Error: No active workspace Caused by: No active workspace. Run: workspace select <name> ``` Running `workspace select` shows that is an unrecognized subcommand: ```bash workspace status Error: No active workspace Caused by: No active workspace. Run: workspace select <name> ``` The help should point to the actual way to activate a workspace: `export SEMTOOLS_WORKSPACE=<name>`

yindo closed this issue

2026-02-16 04:15:07 -05:00

yindo commented

2026-02-16 04:15:07 -05:00

@logan-markewich commented on GitHub (Sep 25, 2025):

Ah yea ive already fixed this actually, just need to make a release. There was a last minute change from workspace select to workspace use

Thanks for checking out the project!

@logan-markewich commented on GitHub (Sep 25, 2025): Ah yea ive already fixed this actually, just need to make a release. There was a last minute change from `workspace select` to `workspace use` Thanks for checking out the project!

yindo commented

2026-02-16 04:15:07 -05:00

@gwtaylor commented on GitHub (Sep 26, 2025):

Thanks! I'll also point out one other part of the docs that was unclear to me as a new user. From the README:

# Create or select a workspace
# Workspaces are stored in ~/.semtools/workspaces/
workspace use my-workspace
> Workspace 'my-workspace' configured.
> To activate it, run:
>   export SEMTOOLS_WORKSPACE=my-workspace
> 
> Or add this to your shell profile (.bashrc, .zshrc, etc.)

# Activate the workspace
export SEMTOOLS_WORKSPACE=my-workspace

What does it mean to "select" a workspace? Is that not what "activation" does?
My experience was that workspace use created and initialized the workspace but it still needed to be activated via the environment variable. I assumed the activation was synonymous with workspace selection.

@gwtaylor commented on GitHub (Sep 26, 2025): Thanks! I'll also point out one other part of the docs that was unclear to me as a new user. From the README: ```README.md # Create or select a workspace # Workspaces are stored in ~/.semtools/workspaces/ workspace use my-workspace > Workspace 'my-workspace' configured. > To activate it, run: > export SEMTOOLS_WORKSPACE=my-workspace > > Or add this to your shell profile (.bashrc, .zshrc, etc.) # Activate the workspace export SEMTOOLS_WORKSPACE=my-workspace ``` What does it mean to "select" a workspace? Is that not what "activation" does? My experience was that `workspace use` created and initialized the workspace but it still needed to be activated via the environment variable. I assumed the activation was synonymous with workspace selection.

yindo referenced this issue

2026-02-16 04:15:15 -05:00

[PR #7] [MERGED] v1.1.0 #23

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: run-llama/semtools#7

BUG: workspace status points to a workspace select <name> command that doesn't exist #7

BUG: `workspace status` points to a `workspace select <name>` command that doesn't exist #7