danielrosehilldanielrosehill/Claude-Hopper/skills/new-claude-here/SKILL.md

new-claude-here

Skill1 starsChanged 7 months agoMITView on GitHub

Open a new Konsole window at the current working directory running a fresh Claude Code CLI session, then close the current Konsole. Use when the user asks for a "new claude session here", "claude here", "jump to a new claude", or "new claude window". Pass "--keep" / "don't close this one" to skip the self-destruct.

In this repository13 other files it gives its agents.
- claude-and-shellSkill
- claude-gridSkill
- clipboard-handoverSkill
- handoverSkill
- handover-with-tasksSkill
- new-claude-atSkill
- new-workspaceSkill
- sideclaudeSkill
- spawn-planning-repoSkill
- start-from-handoverSkill
- start-leftoverSkill
- terminal-hereSkill
- vscode-hereSkill

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Verify a new Konsole PID appeared (poll briefly if needed):
line 22
Distinctive:
If no new PID, ABORT — do not close anything.
line 27
Very specific:
If the user says "keep this one open", "don't close this terminal", or passes --keep, do steps 1–3 only and skip the kill.
line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

New Claude Session Here

Spawns a sibling Claude Code session in a new Konsole window at the current $PWD, then closes the current Konsole so the user lands cleanly in the fresh session.

Why this lives in the session-transfer plugin

The common reason to jump to a fresh Claude session mid-task is that the current session can't pick up changes without a restart — most often after installing a new MCP server, editing settings, or hitting a stuck state. In those cases the user wants session continuity without losing their place. This skill is the "quick jump" path; session-transfer:write-handover / session-transfer:start-from-handover is the "pipe the full context across" path. Offer both when relevant.

Steps (default: self-destruct on)

Snapshot existing Konsole PIDs: before=$(pgrep -x konsole).
Spawn the new Konsole detached:
```
setsid konsole --workdir "$PWD" -e claude >/dev/null 2>&1 &
```
setsid + background keeps it running after the current Claude Code session exits.
Verify a new Konsole PID appeared (poll briefly if needed):
```
after=$(pgrep -x konsole)
comm -13 <(echo "$before" | sort) <(echo "$after" | sort)
```
If no new PID, ABORT — do not close anything. Report the failure.
Warn the user once: "New Konsole verified at PID <n>. Closing this terminal in 3s — the current Claude session will die with it."
Close the current Konsole by killing its window process:
```
(sleep 3 && kill -TERM $(ps -o ppid= -p $PPID | tr -d ' ')) &
```
Rationale: $PPID inside a Claude tool call is the shell; its parent is the Konsole window. Killing the window tears down the shell and this Claude session cleanly.

Keep-current variant

If the user says "keep this one open", "don't close this terminal", or passes --keep, do steps 1–3 only and skip the kill. Report the new session directory.

Notes

The new session is standalone — no shared memory with this one. If the user needs context carried over, suggest running session-transfer:write-handover first.
Report the directory the new session was launched in before self-destructing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free