workspace

Launch named Claude Code sessions in new terminal tabs with optional session resume.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ETdoFresh/claude-marketplace --skill workspace-etdofresh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace
Source: https://github.com/ETdoFresh/claude-marketplace/tree/main/plugins/workspace-launcher/skills/workspace
Command: npx skills add https://github.com/ETdoFresh/claude-marketplace --skill workspace-etdofresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a new Claude Code session with a specific working directory, display name, and resumable session ID requires manually constructing terminal commands that differ between Windows (WSL) and Linux. This Skill automates that entire launch workflow. ## Core Features & Use Cases - Named Session Launch: Opens a new Claude Code session in a new terminal tab with a custom display title, using wt.exe on Windows or a pseudo-TTY on Linux. - Session Resume: Accepts an existing session UUID and attempts --resume first, automatically falling back to --session-id if the resume fails. - Cross-Platform Handling: Detects the platform, converts paths with cygpath on Windows, and provides fallback chains (psmux.exe, cmd.exe) when the primary launcher fails. - Use Case: Run /workspace my-project to instantly open a Claude session rooted at your default workspaces directory, then later resume it with /workspace my-project <session-id>. ## Quick Start Ask the assistant to launch a workspace named "my-project" and it will open a new Claude Code session in your default workspaces directory.

Frequently Asked Questions about workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch a named Claude Code session in a new terminal tab?▼

Run /workspace followed by a display name, such as /workspace my-project. The session opens in a new terminal tab using wt.exe on Windows or a pseudo-TTY via the script command on Linux, with the working directory defaulting to $WORKSPACES_DIR or ~/workspace.

How do I resume an existing Claude Code session by ID?▼

Pass the session UUID as the third argument: /workspace my-project ~/projects/app <session-id>. The launcher first tries claude --resume with that ID, and if the resume fails it falls back to starting a new session with --session-id using the same UUID.

Does the workspace name change the working directory path?▼

No, the workspace name is only a display label for the terminal tab and session title. The working directory is always $WORKSPACES_DIR (default ~/workspace) or the explicitly provided second argument, and the name is never appended to the path.

Does this work on Windows WSL and Linux?▼

Yes, the launcher detects the platform by checking for wt.exe or cmd.exe. On Windows it converts paths with cygpath and uses wt.exe with psmux.exe and cmd.exe fallbacks; on Linux it uses script -qc to allocate a pseudo-TTY and background the session.

What happens if wt.exe or the resume attempt fails?▼

If wt.exe fails, the launcher falls back to psmux.exe, then cmd.exe, and finally the Linux method. If a --resume launch exits non-zero, the same command is retried with --session-id instead, preserving the UUID for later resumption.