alysis-code 0.13.1__tar.gz → 0.13.4__tar.gz

alysis_code-0.13.4/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.4
+Name: alysis-code
+Version: 0.13.4
+Summary: Local CLI coding agent powered by any API.
+Project-URL: Changelog, https://github.com/AlysisAi/alysis-code/blob/main/docs/CHANGELOG.md
+Project-URL: Documentation, https://github.com/AlysisAi/alysis-code/tree/main/docs
+Project-URL: Funding, https://github.com/sponsors/AlysisAi
+Project-URL: Issues, https://github.com/AlysisAi/alysis-code/issues
+Project-URL: Security, https://github.com/AlysisAi/alysis-code/blob/main/.github/SECURITY.md
+Project-URL: Source, https://github.com/AlysisAi/alysis-code
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agent,api,cli,coding-agent,developer-tools,llm
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Requires-Python: >=3.11
+Requires-Dist: click>=8.0.0
+Requires-Dist: cryptography>=50.0.0
+Requires-Dist: ddgs>=9.0.0
+Requires-Dist: h2>=4.4.1
+Requires-Dist: httpcore<2.0.0,>=1.0.0
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: keyring>=25.0.0
+Requires-Dist: packaging>=23.0
+Requires-Dist: pillow>=12.3.0
+Requires-Dist: platformdirs>=4.2.0
+Requires-Dist: prompt-toolkit>=3.0.43
+Requires-Dist: pydantic>=2.6.0
+Requires-Dist: rich>=13.7.1
+Requires-Dist: tiktoken>=0.7.0
+Requires-Dist: typer>=0.12.0
+Requires-Dist: websockets<17.0,>=15.0
+Provides-Extra: dev
+Requires-Dist: editables==0.5; extra == 'dev'
+Requires-Dist: hatchling==1.31.0; extra == 'dev'
+Requires-Dist: pytest>=8.0.0; extra == 'dev'
+Requires-Dist: pyyaml>=6.0.0; extra == 'dev'
+Requires-Dist: ruff>=0.6.0; extra == 'dev'
+Provides-Extra: managed-build
+Requires-Dist: pyinstaller-hooks-contrib==2026.6; extra == 'managed-build'
+Requires-Dist: pyinstaller==6.21.0; extra == 'managed-build'
+Provides-Extra: server
+Requires-Dist: fastapi>=0.115; extra == 'server'
+Requires-Dist: python-multipart>=0.0.9; extra == 'server'
+Requires-Dist: uvicorn[standard]>=0.30; extra == 'server'
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="docs/assets/banner-dark.svg">
+    <img src="docs/assets/banner.svg" alt="Alysis Code — Everyone's Coding Agent" width="720">
+  </picture>
+</p>
+
+<p align="center">
+  Local CLI coding agent that turns plans into reviewed, PR-ready code.<br>
+  Bring your own model. Sandboxed by default.
+</p>
+
+<p align="center">
+  <a href="https://alysiscode.com/">Website</a> ·
+  <a href="https://github.com/AlysisAi/alysis-code/tree/main/docs">Docs</a> ·
+  <a href="https://github.com/AlysisAi/alysis-code/blob/main/docs/CHANGELOG.md">Changelog</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/sponsors/AlysisAi"><img src="https://img.shields.io/github/sponsors/AlysisAi?label=Sponsor&logo=GitHub" alt="GitHub Sponsors"></a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/AlysisAi/alysis-code/actions/workflows/ci.yml"><img src="https://github.com/AlysisAi/alysis-code/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
+  <a href="https://pypi.org/project/alysis-code/"><img src="https://img.shields.io/pypi/v/alysis-code.svg" alt="PyPI version"></a>
+  <a href="https://pypi.org/project/alysis-code/"><img src="https://img.shields.io/pypi/pyversions/alysis-code.svg" alt="Python versions"></a>
+  <a href="https://github.com/AlysisAi/alysis-code/blob/main/LICENSE"><img src="https://img.shields.io/pypi/l/alysis-code.svg" alt="License"></a>
+</p>
+
+---
+
+## Get Started
+
+Alysis Code requires **Python 3.11+** and runs on macOS, Linux, and Windows.
+
+**1 — Install**
+
+```bash
+pipx install alysis-code
+```
+
+**2 — Launch in your project**
+
+```bash
+cd your-project
+alysis-code
+```
+
+The first run opens a guided setup wizard: choose **Use an API key** or **Use an AI subscription**,
+connect a provider, and pick your default model. Re-run it anytime with `alysis-code setup`.
+(`alysis` works too, as a short alias.)
+
+**3 — Start building**
+
+```bash
+alysis-code chat                            # interactive coding session
+alysis-code run "Fix the failing tests"     # one-shot task
+```
+
+Bring your own key from any supported provider — or point Alysis Code at a local endpoint (Ollama,
+LM Studio, vLLM) and run fully offline. The `/config` picker lists every preset. Full walkthrough:
+[Quickstart guide](docs/quickstart.md).
+
+---
+
+## Why Alysis Code
+
+- **Easy to use** — a full coding agent behind a clean, convenient terminal interface that anyone can
+  pick up and play with in minutes: slash commands, interactive pickers, and live status built in.
+- **Built for every developer** — from solo scripts to team servers and CI, the same agent fits every
+  workflow.
+- **[Forge Mode](https://alysiscode.com/docs/concepts/tasks)** — plan-driven execution for larger work:
+  plan, dispatch parallel workers, verify each task, ship PR-ready code.
+- **[Orchestrated subagents](https://alysiscode.com/docs/concepts/agents)** — isolated workers run in
+  parallel, verification is pinned to their exact candidates, and changes apply only after host-side
+  conflict checks.
+- **Free built-in web search** — model-independent `web_search` that works with any provider, at no
+  extra cost.
+- **[Bring your own model](https://alysiscode.com/docs/config/models)** — OpenAI, Anthropic, DeepSeek,
+  Qwen, Gemini, Mistral, Xiaomi MiMo, OpenRouter, xAI, and more — plus local endpoints (Ollama,
+  LM Studio, vLLM) for fully offline use.
+- **[Deeply extensible](https://alysiscode.com/docs/concepts/plugins)** — skills, custom tools, MCP
+  servers, hooks, subagents, and plugins, bundled in one declarative manifest.
+- **[Sandboxed by default](https://alysiscode.com/docs/safety/sandbox-modes)** — Docker or Bubblewrap
+  isolation with an always-on denylist that refuses `rm -rf /`, `curl | sh`, and `sudo` — even in
+  `fullaccess`.
+
+Shell and verification commands default to strict sandboxing. Verification can run outside that
+sandbox only when explicitly configured with `verify_sandbox.mode="off"` or
+`ALYSIS_VERIFY_SANDBOX_MODE=off`.
+
+## Modes & Personas
+
+Two layers control what the agent may do — one enforces, one focuses.
+
+**Execution modes** are the enforcement layer. Choose one per command with `--mode`, switch in chat
+with `/mode`, or set a default with `alysis-code config set default_mode <mode>`:
+
+| Mode | Behavior |
+| --- | --- |
+| `readonly` | Inspection only — no file writes, shell, MCP, or subagent delegation. |
+| `review` | The safe default — previews and asks before every write and shell command. |
+| `auto` | Applies routine edits with fewer prompts; dangerous operations stay blocked. |
+| `fullaccess` | No mode-level prompts for trusted workspaces — the denylist and audit log stay active. |
+
+**Personas** are working postures layered on top. Switch with `/persona`, or cycle with **Tab** in
+the TUI:
+
+| Persona | Posture |
+| --- | --- |
+| `code` | Implementation — the default, full coding workflow. |
+| `architect` | Planning and design — may write markdown documents only. |
+| `ask` | Read-only questions and codebase exploration. |
+| `debug` | Reproduce the failure first, then fix minimally and rerun the reproduction. |
+
+A persona is a convention, never a permission: it can keep or lower your execution mode, but can
+never raise it. Define your own in `.alysis_personas/*.md`.
+[Learn more](https://alysiscode.com/docs/concepts/personas)
+
+## Project Links
+
+- [Website](https://alysiscode.com/)
+- [Documentation](https://alysiscode.com/docs) — also mirrored in [docs/](docs/README.md)
+- [Changelog](docs/CHANGELOG.md)
+- [Contributing](.github/CONTRIBUTING.md) — local setup and PR expectations
+- [Security policy](.github/SECURITY.md) — report vulnerabilities privately, never through public issues
+
+## License
+
+Apache-2.0. You're free to use, modify, and distribute this code, including commercially, as long as
+you keep the attribution and license notices. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
+
+## FAQ
+
+<details>
+<summary><b>Where did Alysis Code come from?</b></summary>
+
+Alysis Code is not a fork. The agent runtime, Forge orchestration, subagent system, terminal
+interface, and sandbox layer were designed and built from zero by the Alysis AI team.
+</details>
+
+<details>
+<summary><b>Is Alysis Code really open source?</b></summary>
+
+Yes. The entire CLI is Apache-2.0 licensed. Bring your own API key from any supported provider, or
+run fully offline against a local endpoint — nothing in the agent requires a paid account.
+</details>
+
+More questions? See the [full FAQ](https://alysiscode.com/docs/faq).
+
+---
+
+**Join the community** — [X](https://x.com/alysiscode) | [GitHub Issues](../../issues)

alysis_code-0.13.4/README.md

@@ -0,0 +1,153 @@
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="docs/assets/banner-dark.svg">
+    <img src="docs/assets/banner.svg" alt="Alysis Code — Everyone's Coding Agent" width="720">
+  </picture>
+</p>
+
+<p align="center">
+  Local CLI coding agent that turns plans into reviewed, PR-ready code.<br>
+  Bring your own model. Sandboxed by default.
+</p>
+
+<p align="center">
+  <a href="https://alysiscode.com/">Website</a> ·
+  <a href="https://github.com/AlysisAi/alysis-code/tree/main/docs">Docs</a> ·
+  <a href="https://github.com/AlysisAi/alysis-code/blob/main/docs/CHANGELOG.md">Changelog</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/sponsors/AlysisAi"><img src="https://img.shields.io/github/sponsors/AlysisAi?label=Sponsor&logo=GitHub" alt="GitHub Sponsors"></a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/AlysisAi/alysis-code/actions/workflows/ci.yml"><img src="https://github.com/AlysisAi/alysis-code/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
+  <a href="https://pypi.org/project/alysis-code/"><img src="https://img.shields.io/pypi/v/alysis-code.svg" alt="PyPI version"></a>
+  <a href="https://pypi.org/project/alysis-code/"><img src="https://img.shields.io/pypi/pyversions/alysis-code.svg" alt="Python versions"></a>
+  <a href="https://github.com/AlysisAi/alysis-code/blob/main/LICENSE"><img src="https://img.shields.io/pypi/l/alysis-code.svg" alt="License"></a>
+</p>
+
+---
+
+## Get Started
+
+Alysis Code requires **Python 3.11+** and runs on macOS, Linux, and Windows.
+
+**1 — Install**
+
+```bash
+pipx install alysis-code
+```
+
+**2 — Launch in your project**
+
+```bash
+cd your-project
+alysis-code
+```
+
+The first run opens a guided setup wizard: choose **Use an API key** or **Use an AI subscription**,
+connect a provider, and pick your default model. Re-run it anytime with `alysis-code setup`.
+(`alysis` works too, as a short alias.)
+
+**3 — Start building**
+
+```bash
+alysis-code chat                            # interactive coding session
+alysis-code run "Fix the failing tests"     # one-shot task
+```
+
+Bring your own key from any supported provider — or point Alysis Code at a local endpoint (Ollama,
+LM Studio, vLLM) and run fully offline. The `/config` picker lists every preset. Full walkthrough:
+[Quickstart guide](docs/quickstart.md).
+
+---
+
+## Why Alysis Code
+
+- **Easy to use** — a full coding agent behind a clean, convenient terminal interface that anyone can
+  pick up and play with in minutes: slash commands, interactive pickers, and live status built in.
+- **Built for every developer** — from solo scripts to team servers and CI, the same agent fits every
+  workflow.
+- **[Forge Mode](https://alysiscode.com/docs/concepts/tasks)** — plan-driven execution for larger work:
+  plan, dispatch parallel workers, verify each task, ship PR-ready code.
+- **[Orchestrated subagents](https://alysiscode.com/docs/concepts/agents)** — isolated workers run in
+  parallel, verification is pinned to their exact candidates, and changes apply only after host-side
+  conflict checks.
+- **Free built-in web search** — model-independent `web_search` that works with any provider, at no
+  extra cost.
+- **[Bring your own model](https://alysiscode.com/docs/config/models)** — OpenAI, Anthropic, DeepSeek,
+  Qwen, Gemini, Mistral, Xiaomi MiMo, OpenRouter, xAI, and more — plus local endpoints (Ollama,
+  LM Studio, vLLM) for fully offline use.
+- **[Deeply extensible](https://alysiscode.com/docs/concepts/plugins)** — skills, custom tools, MCP
+  servers, hooks, subagents, and plugins, bundled in one declarative manifest.
+- **[Sandboxed by default](https://alysiscode.com/docs/safety/sandbox-modes)** — Docker or Bubblewrap
+  isolation with an always-on denylist that refuses `rm -rf /`, `curl | sh`, and `sudo` — even in
+  `fullaccess`.
+
+Shell and verification commands default to strict sandboxing. Verification can run outside that
+sandbox only when explicitly configured with `verify_sandbox.mode="off"` or
+`ALYSIS_VERIFY_SANDBOX_MODE=off`.
+
+## Modes & Personas
+
+Two layers control what the agent may do — one enforces, one focuses.
+
+**Execution modes** are the enforcement layer. Choose one per command with `--mode`, switch in chat
+with `/mode`, or set a default with `alysis-code config set default_mode <mode>`:
+
+| Mode | Behavior |
+| --- | --- |
+| `readonly` | Inspection only — no file writes, shell, MCP, or subagent delegation. |
+| `review` | The safe default — previews and asks before every write and shell command. |
+| `auto` | Applies routine edits with fewer prompts; dangerous operations stay blocked. |
+| `fullaccess` | No mode-level prompts for trusted workspaces — the denylist and audit log stay active. |
+
+**Personas** are working postures layered on top. Switch with `/persona`, or cycle with **Tab** in
+the TUI:
+
+| Persona | Posture |
+| --- | --- |
+| `code` | Implementation — the default, full coding workflow. |
+| `architect` | Planning and design — may write markdown documents only. |
+| `ask` | Read-only questions and codebase exploration. |
+| `debug` | Reproduce the failure first, then fix minimally and rerun the reproduction. |
+
+A persona is a convention, never a permission: it can keep or lower your execution mode, but can
+never raise it. Define your own in `.alysis_personas/*.md`.
+[Learn more](https://alysiscode.com/docs/concepts/personas)
+
+## Project Links
+
+- [Website](https://alysiscode.com/)
+- [Documentation](https://alysiscode.com/docs) — also mirrored in [docs/](docs/README.md)
+- [Changelog](docs/CHANGELOG.md)
+- [Contributing](.github/CONTRIBUTING.md) — local setup and PR expectations
+- [Security policy](.github/SECURITY.md) — report vulnerabilities privately, never through public issues
+
+## License
+
+Apache-2.0. You're free to use, modify, and distribute this code, including commercially, as long as
+you keep the attribution and license notices. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
+
+## FAQ
+
+<details>
+<summary><b>Where did Alysis Code come from?</b></summary>
+
+Alysis Code is not a fork. The agent runtime, Forge orchestration, subagent system, terminal
+interface, and sandbox layer were designed and built from zero by the Alysis AI team.
+</details>
+
+<details>
+<summary><b>Is Alysis Code really open source?</b></summary>
+
+Yes. The entire CLI is Apache-2.0 licensed. Bring your own API key from any supported provider, or
+run fully offline against a local endpoint — nothing in the agent requires a paid account.
+</details>
+
+More questions? See the [full FAQ](https://alysiscode.com/docs/faq).
+
+---
+
+**Join the community** — [X](https://x.com/alysiscode) | [GitHub Issues](../../issues)

{alysis_code-0.13.1 → alysis_code-0.13.4/docs}/CHANGELOG.md

@@ -11,7 +11,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **Renamed from Sylliptor to Alysis Code.** The command is now `alysis`, the
   PyPI package is `alysis-code`, the Python module is `alysis_code`, the
   environment prefix is `ALYSIS_`, and the per-repo directory is `.alysis/`.
-  See [docs/migration-alysis-code.md](docs/migration-alysis-code.md).
+  See [docs/migration-alysis-code.md](migration-alysis-code.md).
 
   Existing installs keep working. Config and credential directories are copied
   to their new locations on first run; the MCP OAuth keyring entry and any
@@ -408,6 +408,66 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   Workspace-target extraction also keeps extensionless dotfiles such as `.npmrc` available to
   verification selection.
 
+## [0.13.4] - 2026-09-05
+
+Model-catalog and TUI-access refresh.
+
+### Added
+
+- Added GPT-6 Astra as the default OpenAI model, with aliases, pricing, context-window,
+  reasoning, OpenRouter, and ChatGPT-subscription metadata.
+- Added newly available first-party and gateway routes for Claude Fable 5.1, Gemini 3.8
+  Flash, Qwen 3.8, GLM-5.3, Kimi K3, Doubao Seed 2.1, DeepSeek V4 snapshots, Grok 4.6,
+  and related hosted variants.
+
+### Changed
+
+- Refreshed every hosted preset's model picker, aliases, validation model, retirement
+  mappings, pricing, context limits, and reasoning contracts against provider catalogs.
+- Updated TUI model labels to preserve vendor naming and made profile pickers show each
+  profile's model, host, active state, retired-model state, and duplicates.
+- Migrated the Perplexity preset from the retiring Sonar Chat Completions endpoint to the
+  Agent API, including hosted web search and saved-profile migration.
+- Replaced the OpenAI economy and validation model with GPT-5.6 Luna and kept
+  GPT-5.3 Codex limited to the Responses preset.
+
+### Fixed
+
+- OpenAI Chat Completions now uses `max_completion_tokens` for GPT-5 and newer models.
+- Native Gemini tool and response schemas are projected onto Gemini's supported OpenAPI
+  subset before requests are sent.
+
+## [0.13.3] - 2026-08-28
+
+### Fixed
+
+- Restored the Ubuntu Python 3.11 and 3.12 CI jobs after the repository cleanup by aligning Ruff
+  formatting, updating moved sandbox contract paths, preserving the security-documentation
+  contract, making immediate shell-output coverage independent of thread scheduling, and allowing
+  harmless floating-point clock precision in deadline coverage.
+
+## [0.13.2] - 2026-08-28
+
+Public launch and repository-layout refresh.
+
+### Added
+
+- A theme-adaptive README banner with dedicated light and dark artwork.
+- `alysis-code` as the canonical executable, while retaining `alysis` as the short alias.
+
+### Changed
+
+- Simplified the public README around installation, core capabilities, modes, and documentation.
+- Moved governance files under `.github/`, release and changelog documents under `docs/`, and
+  sandbox and benchmark sources under `scripts/` for a cleaner repository root.
+- Legacy Sylliptor environment and command compatibility now forwards silently while retaining
+  diagnostic logging for support.
+
+### Fixed
+
+- Device-login approval URLs now remain pinned to the configured Alysis site instead of trusting
+  a backend-provided origin.
+
 ## [0.13.1] - 2026-08-27
 
 Input usability and runtime reliability improvements.

{alysis_code-0.13.1 → alysis_code-0.13.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "alysis-code"
-version = "0.13.1"
+version = "0.13.4"
 description = "Local CLI coding agent powered by any API."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -51,11 +51,11 @@ dependencies = [
 ]
 
 [project.urls]
-Changelog = "https://github.com/AlysisAi/alysis-code/blob/main/CHANGELOG.md"
+Changelog = "https://github.com/AlysisAi/alysis-code/blob/main/docs/CHANGELOG.md"
 Documentation = "https://github.com/AlysisAi/alysis-code/tree/main/docs"
 Funding = "https://github.com/sponsors/AlysisAi"
 Issues = "https://github.com/AlysisAi/alysis-code/issues"
-Security = "https://github.com/AlysisAi/alysis-code/blob/main/SECURITY.md"
+Security = "https://github.com/AlysisAi/alysis-code/blob/main/.github/SECURITY.md"
 Source = "https://github.com/AlysisAi/alysis-code"
 
 [project.optional-dependencies]
@@ -77,10 +77,13 @@ server = [
 ]
 
 [project.scripts]
+# Canonical command.
+alysis-code = "alysis_code.cli:app"
+# Short alias.
 alysis = "alysis_code.cli:app"
 # Deprecated alias kept so muscle memory, shell aliases, CI scripts and IDE
-# configs written against the old name keep working. Prints a one-line notice
-# and forwards. Remove no earlier than the next major release.
+# configs written against the old name keep working. Forwards silently.
+# Remove no earlier than the next major release.
 sylliptor = "alysis_code.cli:legacy_app"
 
 [tool.hatch.build.targets.wheel]
@@ -93,7 +96,7 @@ exclude = [
 [tool.hatch.build.targets.sdist]
 include = [
   "/.gitignore",
-  "/CHANGELOG.md",
+  "/docs/CHANGELOG.md",
   "/LICENSE",
   "/NOTICE",
   "/README.md",

{alysis_code-0.13.1 → alysis_code-0.13.4}/src/alysis_code/__init__.py

@@ -1,3 +1,3 @@
 __all__ = ["__version__"]
 
-__version__ = "0.13.1"
+__version__ = "0.13.4"

{alysis_code-0.13.1 → alysis_code-0.13.4}/src/alysis_code/account_login.py

@@ -26,6 +26,7 @@ import urllib.request
 from collections.abc import Callable
 from dataclasses import dataclass
 from datetime import UTC, datetime
+from urllib.parse import urlsplit
 
 from . import alysis_cloud as cloud
 from .config import (
@@ -302,6 +303,38 @@ def _http_error_message(exc: urllib.error.HTTPError) -> str:
     return f"Login request failed (HTTP {exc.code})."
 
 
+def _approval_url(server_url: str, *, user_code: str) -> str:
+    """Build the /activate URL to open, pinning the host to the configured site.
+
+    The device endpoint returns its own ``verification_url`` /
+    ``verification_url_complete``. Opening that verbatim lets the *server*
+    decide which website the CLI sends the user to — which is how a deployment
+    still carrying the pre-rebrand host (``sylliptor.alysisai.com``) kept
+    launching the retired site long after the client had been rebranded, and
+    which would equally let a compromised or misconfigured backend point
+    sign-in anywhere. Only the path and query are taken from the response; the
+    origin always comes from ``alysis_cloud.site_url()`` (env-overridable via
+    ALYSIS_SITE_URL for staging/local stubs), so the host the user lands on is
+    the one this client trusts.
+    """
+    base = cloud.site_url()
+    path = "/activate"
+    query = f"code={user_code}" if user_code else ""
+
+    if server_url:
+        try:
+            parts = urlsplit(server_url)
+        except ValueError:
+            parts = None
+        if parts is not None:
+            if parts.path:
+                path = parts.path if parts.path.startswith("/") else f"/{parts.path}"
+            if parts.query:
+                query = parts.query
+
+    return f"{base}{path}?{query}" if query else f"{base}{path}"
+
+
 def _request_device_code() -> _DeviceGrant:
     client_name = f"alysis-cli @ {platform.node() or 'unknown-host'}"[:80]
     body = _post_json(cloud.device_code_url(), {"client_name": client_name})
@@ -311,11 +344,10 @@ def _request_device_code() -> _DeviceGrant:
     if not device_code or not user_code:
         raise AlysisLoginError("Login service did not return a device code.")
 
-    verification_url = str(
-        body.get("verification_url_complete") or body.get("verification_url") or ""
-    ).strip()
-    if not verification_url:
-        verification_url = f"{cloud.activate_url()}?code={user_code}"
+    verification_url = _approval_url(
+        str(body.get("verification_url_complete") or body.get("verification_url") or "").strip(),
+        user_code=user_code,
+    )
 
     try:
         interval_s = max(float(body.get("interval", _DEFAULT_POLL_INTERVAL_S)), 0.0)

{alysis_code-0.13.1 → alysis_code-0.13.4}/src/alysis_code/branding.py

@@ -4,7 +4,10 @@ The CLI shipped as "Sylliptor" (package ``sylliptor-agent-cli``, command
 ``sylliptor``, env prefix ``SYLLIPTOR_``) before being renamed to Alysis Code.
 Everything a user could have written down — env vars in a CI config, a
 ``.sylliptor/`` directory committed to their repo, a keyring entry holding MCP
-OAuth tokens — still resolves, with a one-time deprecation notice. See
+OAuth tokens — still resolves. The fallbacks are deliberately *silent*: they
+are a courtesy to people who already migrated once, not something to announce
+above the TUI on every launch. Each one is recorded to the log at warning level
+so a support session can still see which legacy input was used. See
 ``docs/migration-alysis-code.md`` for the removal timeline.
 """
 
@@ -14,7 +17,6 @@ import logging
 import os
 import shutil
 import threading
-import warnings
 from collections.abc import Mapping
 from importlib import metadata as importlib_metadata
 from pathlib import Path
@@ -49,8 +51,6 @@ MIGRATION_MARKER_NAME = ".migrated-to-alysis"
 
 _notice_lock = threading.Lock()
 _legacy_env_seen: dict[str, str] = {}
-_migrated_paths: dict[str, str] = {}
-_legacy_paths_in_use: dict[str, str] = {}
 
 
 def legacy_env_name(name: str) -> str | None:
@@ -61,15 +61,12 @@ def legacy_env_name(name: str) -> str | None:
 
 
 def _record_legacy_env(legacy: str, current: str) -> None:
+    """Log a legacy variable read, once per variable, without warning the user."""
     with _notice_lock:
         if legacy in _legacy_env_seen:
             return
         _legacy_env_seen[legacy] = current
-    message = (
-        f"{legacy} is deprecated and will be removed in a future release; rename it to {current}."
-    )
     LOGGER.warning("legacy_env_var legacy=%s current=%s", legacy, current)
-    warnings.warn(message, DeprecationWarning, stacklevel=3)
 
 
 def env_get(name: str, default: str | None = None) -> str | None:
@@ -121,26 +118,14 @@ def with_legacy_env_aliases(env: Mapping[str, str]) -> dict[str, str]:
     return merged
 
 
-def consume_legacy_notices() -> list[str]:
-    """Drain accumulated deprecation notices for the CLI to surface once."""
+def reset_legacy_tracking() -> None:
+    """Forget which legacy inputs have been seen, so logging repeats.
+
+    Only the per-process de-duplication state; nothing user-visible depends on
+    it. Tests use it to isolate cases that each expect a fresh log line.
+    """
     with _notice_lock:
-        env_items = sorted(_legacy_env_seen.items())
-        migrated = sorted(_migrated_paths.items())
-        in_use = sorted(_legacy_paths_in_use.items())
         _legacy_env_seen.clear()
-        _migrated_paths.clear()
-        _legacy_paths_in_use.clear()
-
-    notices = [
-        f"Environment variable {legacy} is deprecated — use {current}."
-        for legacy, current in env_items
-    ]
-    notices.extend(f"Copied {legacy} to {current}." for legacy, current in migrated)
-    notices.extend(
-        f"Using legacy directory {legacy}; rename it to {current} when convenient."
-        for legacy, current in in_use
-    )
-    return notices
 
 
 def _github_owner_from_url(url: str) -> str | None:
@@ -223,8 +208,6 @@ def _migrate_legacy_dir(current: Path, legacy: Path) -> Path:
         # Marker is an optimisation; a missing one only costs a redundant check.
         pass
 
-    with _notice_lock:
-        _migrated_paths.setdefault(str(legacy), str(current))
     LOGGER.info("legacy_dir_migrated legacy=%s current=%s", legacy, current)
     return current
 
@@ -259,8 +242,7 @@ def resolve_project_dir(root: Path) -> Path:
         return current
     legacy = root / LEGACY_PROJECT_DIR_NAME
     if legacy.is_dir():
-        with _notice_lock:
-            _legacy_paths_in_use.setdefault(str(legacy), str(current))
+        LOGGER.debug("legacy_project_dir_in_use legacy=%s current=%s", legacy, current)
         return legacy
     return current
 

{alysis_code-0.13.1 → alysis_code-0.13.4}/src/alysis_code/cli.py

@@ -34,16 +34,11 @@ from .cli_impl.commands.cli_surface import *
 def legacy_app() -> None:
     """Entry point for the deprecated ``sylliptor`` command.
 
-    Behaves identically to ``alysis``; the only difference is a notice on
-    stderr, so piping stdout to another program is unaffected.
+    Forwards to ``alysis`` silently. The alias exists so muscle memory, shell
+    aliases, CI scripts and IDE configs written against the old name keep
+    working — announcing that on every launch only put a stray line above the
+    TUI. The removal timeline lives in ``docs/migration-alysis-code.md``.
     """
-    import sys as _sys
-
-    print(
-        "note: 'sylliptor' has been renamed to 'alysis'. This alias still works "
-        "but will be removed in a future release.",
-        file=_sys.stderr,
-    )
     app()