kylon-cli 0.3.10-next.710 → 0.3.10-next.712

package/README.md

@@ -91,17 +91,19 @@ question; on a machine without one (CI, a headless box) it passes `--yes` and
 the browser confirmation is the only gate.
 
 It detects, offline and read-only, the project (the nearest `.git` ancestor,
-whose directory name becomes the workspace name), the `CLAUDE.md` instruction
-files (project, `.claude/`, and user-level), the skill directories under
+named from its `origin` repository when available and otherwise from its
+directory), the `CLAUDE.md` instruction files (project, `.claude/`, and
+user-level), the skill directories under
 `.claude/skills/` that carry a `SKILL.md`, and the project's Claude Code memory
 entries. Env files, credential-shaped content, binaries, empty files, oversized
-files, and symlinks are never uploaded. It prints what it found, asks once
-(Enter confirms), then opens your browser: you sign in or sign up, review the
-proposal, rename or untick anything, and press one button. The workspace, its
-Rooms, the agent, its persona, its skills, and its memory are created there;
-the terminal then connects this computer's agent and starts the local runtime.
-Nothing durable exists until you press that button — an abandoned run leaves
-only expiring server-side state.
+files, and symlinks are never uploaded. Its terminal summary shows the semantic
+project name and its source separately from the physical checkout root. It then
+asks once (Enter confirms) and opens your browser: you sign in or sign up,
+review the proposal, rename or untick anything, and press one button. The
+workspace, its Rooms, the agent, its persona, its skills, and its memory are
+created there; the terminal then connects this computer's agent and starts the
+local runtime. Nothing durable exists until you press that button — an
+abandoned run leaves only expiring server-side state.
 
 It never attaches to an existing workspace. For that, use `kylon login` and
 create the agent in the Web UI.
@@ -139,7 +141,9 @@ requires `--yes`) prints
 `{ ok, server_url, workspace_id, workspace_name, agent_id, agent_name, room_id, workspace_url, credentials_path }`
 on stdout — never the API key or the link token — while the browser URL and
 user code go to stderr so a human can still complete the confirmation.
-`--workspace-name` and `--agent-name` override the detected names,
+`--project-name` overrides the detected project and suggested Room name;
+unless `--workspace-name` is also given, it becomes the workspace name too.
+`--workspace-name` and `--agent-name` override those detected names,
 `--cwd <dir>` detects somewhere other than the working directory, `--no-start`
 connects without starting the runtime, and `--no-modify-path` leaves shell
 profiles untouched.

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.3.10-next.710",
-  "fingerprint": "d55f44c247874e7b5b642580ce4909416f6caa5a90ac3e91031cc43ceca45dce",
-  "source_commit": "b26da6f0d615953f21b01f76691ac4b03e0401ba"
+  "version": "0.3.10-next.712",
+  "fingerprint": "98a461c873abd9b56ae3647e0fa1603420a8cdddc8ce893abbe4b8f58b39d45a",
+  "source_commit": "c7ecb44aec255ed1e69a5d42e9d3065e69d45bd1"
 }