ms-tau-sdk 1.2.12.dev21__tar.gz → 1.2.13.dev22__tar.gz

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Changelog
 
+## Unreleased
+
+- Local mode no longer needs a token in the environment or in the project `.env`. With neither
+  `MAINSEQUENCE_ACCESS_TOKEN` nor `MAINSEQUENCE_REFRESH_TOKEN` set, it asks a Main Sequence CLI
+  for the access token with `mainsequence auth token --json`: log in once with
+  `mainsequence login`. The SDK looks for the CLI in the new `MAINSEQUENCE_CLI` setting, then
+  beside the Python interpreter, then on `PATH`. It keeps the token in memory, reuses it until 60
+  seconds before it expires, and asks again after a rejected request. It refuses an answer for
+  another backend. A missing CLI, a CLI too old for the command, a missing or expired session, a
+  machine without a credential store, a time-out, and malformed output each have their own error.
+  The SDK still does not depend on or import the `mainsequence` package and does not read the
+  CLI's credential store. The token pair stays supported in the process environment, for
+  launchers and CI, and with both tokens set the CLI is never run. A pair read from the project
+  `.env` file still works but is deprecated: startup logs one warning that names the file and the
+  two variables, and `mainsequence refresh-token` run in that directory removes them. `/health`
+  and `/ready` report the source in `mainsequence_auth_source` (`cli`, `environment`, or
+  `env_file`; `null` in managed mode), and Tau Board shows it in Connect. The owner scope of local
+  chat sessions and direct A2A conversations is derived from the subject of the CLI token, so a
+  user keeps the same local sessions with either source. See the 2026-09-30 amendments of ADR 0005
+  and ADR 0017.
+- Tau Board again reads the local state the SDK writes. 1.2.12 raised the local SQLite schema
+  version to 6 without raising the version Tau Board accepts, so the board refused every store
+  that 1.2.12 had created or opened: the State, session, Task, and Task-log views returned
+  "Unknown Tau local SQLite schema version". Schema 6 only adds the `local_chat_sessions` table,
+  and the board's queries are unchanged. The board still accepts exactly one schema version, so a
+  store last opened by 1.2.11 or earlier is refused until Tau starts once and migrates it. A Board
+  test now reads a store written by the SDK's local backend, so a schema change the board has not
+  followed fails the Board suite.
+
 ## 1.2.12 — 2026-09-27
 
 - Local `/api/chat` sessions now survive a UI reload and a Tau restart. Local mode records each chat

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-tau-sdk
-Version: 1.2.12.dev21
+Version: 1.2.13.dev22
 Summary: Workspace-bound Tau application primitives for Main Sequence projects
 Project-URL: Changelog, https://github.com/mainsequence-sdk/ms-tau-sdk/blob/development/CHANGELOG.md
 Project-URL: Documentation, https://github.com/mainsequence-sdk/ms-tau-sdk/tree/development/docs
@@ -129,9 +129,9 @@ project selects a provider and model explicitly, while Main Sequence still autho
 the provider credential and supplies the live MCP catalog:
 
 ```bash
+mainsequence login   # once; the session is kept by the CLI, not in .env
+
 export MAINSEQUENCE_AUTH_MODE=jwt
-export MAINSEQUENCE_ACCESS_TOKEN="<exported-user-access-token>"
-export MAINSEQUENCE_REFRESH_TOKEN="<exported-user-refresh-token>"
 export TAU_LOCAL_MODE=true
 export TAU_LOCAL_PROVIDER=openai
 export TAU_LOCAL_MODEL=gpt-5.4
@@ -139,10 +139,21 @@ export TAU_LOCAL_MODEL=gpt-5.4
 uv run ms-tau
 ```
 
-The normal Main Sequence login or project launcher may provision those JWT variables, but
-`ms-tau-sdk` does not install, import, or invoke the `mainsequence` Python package. It consumes the
-environment handoff and public refresh API directly. Provider secrets are never environment
-settings and are never persisted locally.
+Log in once with the Main Sequence CLI. Local mode then asks that CLI for a short-lived access
+token with `mainsequence auth token --json`, and again when the token is about to expire. No token
+is exported and none is written to the project `.env`. The SDK looks for the CLI in
+`MAINSEQUENCE_CLI`, then beside the Python interpreter, then on `PATH`. `ms-tau-sdk` does not
+install or import the `mainsequence` Python package and does not read the CLI's credential store.
+
+Launchers and CI can hand the process a token pair instead. With both variables set, the SDK
+uses them and the public refresh API and never runs the CLI:
+
+```bash
+export MAINSEQUENCE_ACCESS_TOKEN="<user-access-token>"
+export MAINSEQUENCE_REFRESH_TOKEN="<user-refresh-token>"
+```
+
+Provider secrets are never environment settings and are never persisted locally.
 
 Local conversations and public A2A Tasks are stored at
 `~/.tau/mainsequence/<workspace-hash>/runtime.sqlite3`; an omitted chat `sessionUid` uses the
@@ -243,7 +254,8 @@ are not bundled into the SDK. Main Sequence transport and protocol behavior rema
 ## Included capabilities
 
 - FastAPI application construction and lifecycle management
-- runtime-credential exchange, local user-JWT refresh, and authenticated Main Sequence access
+- runtime-credential exchange, local sign-in through the Main Sequence CLI session or a user-JWT
+  environment pair, and authenticated Main Sequence access
 - provider validation and credential hydration
 - durable Tau sessions, leases, restore, persistence, cancellation, eviction, and shutdown
 - local Tau execution without backend AgentSession pre-creation

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/README.md

@@ -98,9 +98,9 @@ project selects a provider and model explicitly, while Main Sequence still autho
 the provider credential and supplies the live MCP catalog:
 
 ```bash
+mainsequence login   # once; the session is kept by the CLI, not in .env
+
 export MAINSEQUENCE_AUTH_MODE=jwt
-export MAINSEQUENCE_ACCESS_TOKEN="<exported-user-access-token>"
-export MAINSEQUENCE_REFRESH_TOKEN="<exported-user-refresh-token>"
 export TAU_LOCAL_MODE=true
 export TAU_LOCAL_PROVIDER=openai
 export TAU_LOCAL_MODEL=gpt-5.4
@@ -108,10 +108,21 @@ export TAU_LOCAL_MODEL=gpt-5.4
 uv run ms-tau
 ```
 
-The normal Main Sequence login or project launcher may provision those JWT variables, but
-`ms-tau-sdk` does not install, import, or invoke the `mainsequence` Python package. It consumes the
-environment handoff and public refresh API directly. Provider secrets are never environment
-settings and are never persisted locally.
+Log in once with the Main Sequence CLI. Local mode then asks that CLI for a short-lived access
+token with `mainsequence auth token --json`, and again when the token is about to expire. No token
+is exported and none is written to the project `.env`. The SDK looks for the CLI in
+`MAINSEQUENCE_CLI`, then beside the Python interpreter, then on `PATH`. `ms-tau-sdk` does not
+install or import the `mainsequence` Python package and does not read the CLI's credential store.
+
+Launchers and CI can hand the process a token pair instead. With both variables set, the SDK
+uses them and the public refresh API and never runs the CLI:
+
+```bash
+export MAINSEQUENCE_ACCESS_TOKEN="<user-access-token>"
+export MAINSEQUENCE_REFRESH_TOKEN="<user-refresh-token>"
+```
+
+Provider secrets are never environment settings and are never persisted locally.
 
 Local conversations and public A2A Tasks are stored at
 `~/.tau/mainsequence/<workspace-hash>/runtime.sqlite3`; an omitted chat `sessionUid` uses the
@@ -212,7 +223,8 @@ are not bundled into the SDK. Main Sequence transport and protocol behavior rema
 ## Included capabilities
 
 - FastAPI application construction and lifecycle management
-- runtime-credential exchange, local user-JWT refresh, and authenticated Main Sequence access
+- runtime-credential exchange, local sign-in through the Main Sequence CLI session or a user-JWT
+  environment pair, and authenticated Main Sequence access
 - provider validation and credential hydration
 - durable Tau sessions, leases, restore, persistence, cancellation, eviction, and shutdown
 - local Tau execution without backend AgentSession pre-creation

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/packages/tau-board/src/ms_tau_board/state.py

@@ -9,7 +9,9 @@ from contextlib import closing
 from pathlib import Path
 from typing import Any
 
-SCHEMA_VERSION = "5"
+# The version `ms_tau_sdk.backend.local` stamps on the store. The board never imports the SDK,
+# so this follows it by hand.
+SCHEMA_VERSION = "6"
 TABLES = (
     "sessions",
     "entries",

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/packages/tau-board/src/ms_tau_board/static/app.js

@@ -210,6 +210,7 @@ async function checkConnection() {
   detailLine(box, "Mode", result.health.mode);
   detailLine(box, "Version", result.health.version);
   detailLine(box, "Ready", result.ready ? "Yes" : "No");
+  detailLine(box, "Credential source", result.health.mainsequence_auth_source);
   detailLine(box, "Workspace digest", result.health.workspace_digest);
   detailLine(box, "State directory", result.stateDir);
   detailLine(box, "MCP tools", result.health.mcp_tool_count);

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/packages/tau-board/src/ms_tau_board/static/index.html

@@ -192,7 +192,7 @@
             <button class="button is-primary" id="settings-apply-board">Apply to this session</button>
             <p class="help mt-2">This updates the selected profile immediately. It does not write <code>.env</code>.</p>
           </div>
-          <div class="box"><h2 class="title is-6">Credential presence</h2><p class="help mb-3">Board process and local <code>.env</code> are shown separately. Credential values are never sent to the browser.</p><div id="settings-credentials" class="detail-list"></div></div>
+          <div class="box"><h2 class="title is-6">Credential presence</h2><p class="help mb-3">Board process and local <code>.env</code> are shown separately. Credential values are never sent to the browser. A Tau process that uses the Main Sequence CLI session needs no token here. Connect shows its credential source.</p><div id="settings-credentials" class="detail-list"></div></div>
         </div>
         <div class="column">
           <div class="box">

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ms-tau-sdk"
-version = "1.2.12.dev21"
+version = "1.2.13.dev22"
 description = "Workspace-bound Tau application primitives for Main Sequence projects"
 readme = "README.md"
 requires-python = ">=3.13"

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/src/ms_tau_sdk/agent_skills/tau_local_development/SKILL.md

@@ -11,14 +11,15 @@ an offline, mock-provider, or mock-MCP mode.
 
 ## Start the process
 
-Obtain the user's access and refresh JWTs through the supported Main Sequence login or
-project-launcher flow. The SDK consumes that environment handoff directly; it does not install,
-import, or invoke the `mainsequence` Python package and does not read its private credential store.
+The user logs in once with a Main Sequence CLI that provides `mainsequence auth token`. Local mode
+then asks that CLI for a short-lived access token, at startup and again when the token is about to
+expire. No token is exported and none is written to the project `.env`. The SDK does not install or
+import the `mainsequence` Python package and does not read the CLI's private credential store.
 
 ```bash
+mainsequence login   # once; the session is kept by the CLI, not in .env
+
 export MAINSEQUENCE_AUTH_MODE=jwt
-export MAINSEQUENCE_ACCESS_TOKEN="<user-access-token>"
-export MAINSEQUENCE_REFRESH_TOKEN="<user-refresh-token>"
 export TAU_LOCAL_MODE=true
 export TAU_LOCAL_PROVIDER="<provider>"
 export TAU_LOCAL_MODEL="<model>"
@@ -28,12 +29,20 @@ export TAU_LOCAL_THINKING="<thinking-level>"
 uv run ms-tau
 ```
 
-Set `MAINSEQUENCE_ENDPOINT` only for a non-default platform endpoint. Local mode binds to
-`127.0.0.1:8787` by default. Treat an explicit public bind as privileged exposure: each accepted
-request can use the authenticated user's live Main Sequence permissions.
+The SDK looks for the CLI in `MAINSEQUENCE_CLI`, then beside the Python interpreter that runs
+`ms-tau`, then on `PATH`. Launchers and CI can export `MAINSEQUENCE_ACCESS_TOKEN` and
+`MAINSEQUENCE_REFRESH_TOKEN` instead. With both set, the SDK uses that pair and never runs the
+CLI. Do not add token lines to `.env`. A pair found there still works, but it is deprecated and
+startup logs a warning. `mainsequence refresh-token` run in that directory removes the lines.
+
+Set `MAINSEQUENCE_ENDPOINT` only for a non-default platform endpoint. The CLI session must be for
+the same endpoint. Local mode binds to `127.0.0.1:8787` by default. Treat an explicit public bind
+as privileged exposure: each accepted request can use the authenticated user's live Main Sequence
+permissions.
 
 Never place JWTs or provider credentials in source control, `.tau`, copied skills, command output,
-or debugging artifacts. The user JWT is sent only to Main Sequence. Main Sequence validates the
+or debugging artifacts. Do not run `mainsequence auth token` to read its output: it prints the
+access token. The user JWT is sent only to Main Sequence. Main Sequence validates the
 explicit `TAU_LOCAL_PROVIDER` and `TAU_LOCAL_MODEL`, returns provider-control evidence, and hydrates
 the provider credential used for inference. Provider secrets are neither environment settings nor
 local state.
@@ -45,7 +54,7 @@ local state.
 | Agent or AgentSession registration | Never created or updated |
 | Chat history, snapshots, leases, activity, and cancellation | Workspace SQLite |
 | Public A2A Message and Task state | Workspace SQLite |
-| Main Sequence authentication and token refresh | Remote, using the exported JWT pair |
+| Main Sequence authentication and token refresh | Remote. The token comes from the Main Sequence CLI session, or from an exported JWT pair |
 | Provider authorization, hydration, and inference | Remote and real |
 | Main Sequence MCP catalog and tool calls | Remote and real; platform mutations remain possible |
 | Project instructions, skills, hooks, and extensions | Normal repository `.tau` composition |
@@ -189,7 +198,8 @@ platform resources under the authenticated user's permissions.
 
 Check the process in this order:
 
-1. `GET /health` reports `mode: local` and safe composition diagnostics.
+1. `GET /health` reports `mode: local`, safe composition diagnostics, and
+   `mainsequence_auth_source`: `cli`, `environment`, or `env_file`.
 2. `GET /ready` confirms user authentication, provider control, local storage, and MCP readiness.
 3. `GET /version` reports the expected installed SDK release.
 4. A chat request without `sessionUid` returns an effective identifier in
@@ -203,8 +213,10 @@ Check the process in this order:
 ## Classify failures
 
 - Startup setting failure: inspect the exact missing or conflicting environment variable.
-- Authentication failure: refresh or re-export the JWT pair; do not substitute a runtime
-  credential in local mode.
+- Authentication failure: read the error, which names its remedy. The user runs
+  `mainsequence login`, upgrades a Main Sequence CLI that is too old for `auth token`, sets
+  `MAINSEQUENCE_CLI`, or provides the JWT pair. With an exported pair, export a fresh one. Do not
+  substitute a runtime credential in local mode.
 - Provider/model rejection: verify the exact configured names against the authenticated live
   catalog; do not silently select a different model.
 - OpenAI-compatible transport failure: open the Task's failure incident in Tau Board. Use its

{ms_tau_sdk-1.2.12.dev21 → ms_tau_sdk-1.2.13.dev22}/src/ms_tau_sdk/application.py

@@ -4,7 +4,7 @@ from __future__ import annotations
 
 from dataclasses import dataclass
 
-from ms_tau_sdk.backend.auth import BackendAuth, JWTAuth, RuntimeCredentialAuth
+from ms_tau_sdk.backend.auth import BackendAuth, RuntimeCredentialAuth, local_mode_auth
 from ms_tau_sdk.backend.client import MainSequenceClient
 from ms_tau_sdk.backend.local import LocalDevelopmentBackend
 from ms_tau_sdk.providers.factory import ProviderFactory
@@ -28,7 +28,7 @@ class ApplicationServices:
         auth: BackendAuth
         backend: MainSequenceClient
         if settings.local_mode:
-            auth = JWTAuth(settings)
+            auth = local_mode_auth(settings)
             services_client = MainSequenceClient(settings, auth)
             backend = LocalDevelopmentBackend(settings, services_client)
         else: