xtralab 0.6.0 → 0.7.0

package/README.md

@@ -82,6 +82,36 @@ See the [`jupyter-server-mcp` README][mcp] for other MCP clients.
 [mcp]: https://github.com/jupyter-ai-contrib/jupyter-server-mcp
 [mcp-spec]: https://modelcontextprotocol.io
 
+## Agent skill
+
+xtralab ships an [Agent Skills][skills] entry at [`agent-skill/`](./agent-skill)
+that teaches any coding agent how to customize JupyterLab from plain-English
+requests like "hide the status bar", "change the theme", or "add a language
+server". The same SKILL.md file works with Claude Code, Codex CLI, Gemini CLI,
+GitHub Copilot, and other tools that read the Agent Skills format.
+
+For Claude Code, this repository doubles as a one-plugin marketplace. Inside a
+Claude Code session:
+
+```text
+/plugin marketplace add jtpio/xtralab
+/plugin install xtralab-skills@xtralab
+```
+
+For agents that read from `~/.agents/skills/`, such as Codex CLI or Gemini CLI,
+clone and copy the skill directory:
+
+```bash
+git clone --depth=1 https://github.com/jtpio/xtralab.git /tmp/xtralab
+mkdir -p ~/.agents/skills
+cp -r /tmp/xtralab/agent-skill/skills/customize-jupyterlab ~/.agents/skills/
+```
+
+See [`agent-skill/README.md`](./agent-skill/README.md) for additional install
+paths, the list of supported agents, and what the skill knows.
+
+[skills]: https://agentskills.io
+
 ## Language servers
 
 xtralab ships [`jupyterlab-lsp`][lsp] with two language servers pre-registered:

package/lib/launcher/dashboard.js

@@ -91,13 +91,28 @@ function LauncherDashboardComponent(props) {
         }
     }, [commands, cwd, onAgentLaunch]);
     const launchNotebook = React.useCallback(async () => {
-        // No `kernelName` — let the notebook extension fall back to the default
-        // kernel or prompt the user, matching the stock launcher's notebook
-        // tile behavior.
-        const result = (await commands.execute('notebook:create-new', {
-            cwd
+        // Open a fresh notebook with no kernel attached — equivalent to clicking
+        // "No Kernel" in the Select Kernel dialog. `notebook:create-new` always
+        // routes through that dialog when no kernelName is given, so drive the
+        // underlying docmanager steps directly and pass `shouldStart: false` to
+        // suppress kernel selection. The user picks a kernel from the notebook
+        // toolbar when they're ready.
+        const file = (await commands.execute('docmanager:new-untitled', {
+            path: cwd,
+            type: 'notebook'
+        }));
+        if (!file) {
+            return;
+        }
+        const result = (await commands.execute('docmanager:open', {
+            path: file.path,
+            factory: 'Notebook',
+            kernelPreference: { shouldStart: false, canStart: true }
         }));
         if (result) {
+            // Match `notebook:create-new`'s post-open marker so the first manual
+            // save offers a rename instead of overwriting the auto-generated name.
+            result.isUntitled = true;
             onAgentLaunch(result);
         }
     }, [commands, cwd, onAgentLaunch]);

package/lib/topBar/index.js

@@ -52,6 +52,18 @@ const plugin = {
     activate: (app, labShell, translator) => {
         const { commands } = app;
         const trans = (translator !== null && translator !== void 0 ? translator : nullTranslator).load('jupyterlab');
+        // The upstream toggle-{left,right}-area commands derive `isEnabled` from
+        // `!labShell.isEmpty(side)` but don't fire `commandChanged` when widgets
+        // move in or out of a side area. `CommandToolbarButton` only re-renders on
+        // `commandChanged` for its own id, so the buttons need an explicit notify
+        // whenever the shell layout shifts — `layoutModified` covers each side
+        // handler's `_updated` (add/remove, expand/collapse), keeping both
+        // `isEnabled` and `isToggled` in sync.
+        labShell.layoutModified.connect(() => {
+            for (const spec of BUTTONS) {
+                commands.notifyCommandChanged(spec.command);
+            }
+        });
         // Defer to `app.restored` so the upstream toggle commands are already in
         // the registry: `CommandToolbarButton` renders nothing until its command
         // exists and only re-renders on `commandChanged` of type `changed` /

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "xtralab",
-    "version": "0.6.0",
+    "version": "0.7.0",
     "description": "An opinionated JupyterLab meta-package that bundles a curated set of extensions, ships a path-first file browser, renders jupyterlab-git's text, notebook and image diffs with its own viewers, and applies a quieter default workspace configuration.",
     "keywords": [
         "jupyter",

package/src/launcher/dashboard.tsx

@@ -3,6 +3,7 @@ import * as React from 'react';
 import type { CommandRegistry } from '@lumino/commands';
 import type { ReadonlyPartialJSONObject } from '@lumino/coreutils';
 import { Poll } from '@lumino/polling';
+import type { IDocumentWidget } from '@jupyterlab/docregistry';
 import {
   LabIcon,
   ReactWidget,
@@ -193,13 +194,28 @@ function LauncherDashboardComponent(
   }, [commands, cwd, onAgentLaunch]);
 
   const launchNotebook = React.useCallback(async () => {
-    // No `kernelName` — let the notebook extension fall back to the default
-    // kernel or prompt the user, matching the stock launcher's notebook
-    // tile behavior.
-    const result = (await commands.execute('notebook:create-new', {
-      cwd
-    })) as Widget | undefined;
+    // Open a fresh notebook with no kernel attached — equivalent to clicking
+    // "No Kernel" in the Select Kernel dialog. `notebook:create-new` always
+    // routes through that dialog when no kernelName is given, so drive the
+    // underlying docmanager steps directly and pass `shouldStart: false` to
+    // suppress kernel selection. The user picks a kernel from the notebook
+    // toolbar when they're ready.
+    const file = (await commands.execute('docmanager:new-untitled', {
+      path: cwd,
+      type: 'notebook'
+    })) as { path: string } | undefined;
+    if (!file) {
+      return;
+    }
+    const result = (await commands.execute('docmanager:open', {
+      path: file.path,
+      factory: 'Notebook',
+      kernelPreference: { shouldStart: false, canStart: true }
+    })) as IDocumentWidget | undefined;
     if (result) {
+      // Match `notebook:create-new`'s post-open marker so the first manual
+      // save offers a rename instead of overwriting the auto-generated name.
+      result.isUntitled = true;
       onAgentLaunch(result);
     }
   }, [commands, cwd, onAgentLaunch]);

package/src/topBar/index.ts

@@ -86,6 +86,19 @@ const plugin: JupyterFrontEndPlugin<void> = {
     const { commands } = app;
     const trans = (translator ?? nullTranslator).load('jupyterlab');
 
+    // The upstream toggle-{left,right}-area commands derive `isEnabled` from
+    // `!labShell.isEmpty(side)` but don't fire `commandChanged` when widgets
+    // move in or out of a side area. `CommandToolbarButton` only re-renders on
+    // `commandChanged` for its own id, so the buttons need an explicit notify
+    // whenever the shell layout shifts — `layoutModified` covers each side
+    // handler's `_updated` (add/remove, expand/collapse), keeping both
+    // `isEnabled` and `isToggled` in sync.
+    labShell.layoutModified.connect(() => {
+      for (const spec of BUTTONS) {
+        commands.notifyCommandChanged(spec.command);
+      }
+    });
+
     // Defer to `app.restored` so the upstream toggle commands are already in
     // the registry: `CommandToolbarButton` renders nothing until its command
     // exists and only re-renders on `commandChanged` of type `changed` /