lean-probe 0.2.0__tar.gz → 0.2.2__tar.gz

{lean_probe-0.2.0/src/lean_probe.egg-info → lean_probe-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lean-probe
-Version: 0.2.0
+Version: 0.2.2
 Summary: Fast Lean 4 proof feedback for agents, powered by LeanInteract.
 Author: LeanProbe contributors
 License-Expression: MIT
@@ -52,8 +52,9 @@ acceptance.
 ## MCP Tools
 
 LeanProbe exposes the MCP server name `lean-probe` and the tools
-`lean_probe_prepare`, `lean_probe_check`, `lean_probe_feedback`,
-`lean_probe_state`, `lean_probe_step`, and `lean_probe_close_state`.
+`lean_probe_capabilities`, `lean_probe_prepare`, `lean_probe_check`,
+`lean_probe_feedback`, `lean_probe_state`, `lean_probe_step`, and
+`lean_probe_close_state`.
 
 For MCP parameter details, result-field semantics, and `feedback_lean` examples,
 see [AGENT.md](AGENT.md).
@@ -96,6 +97,21 @@ The benchmark suite measures two cases:
 - sequential same-file checks: prepare a header once, then advance declaration by
   declaration with env reuse.
 
+## How It Differs From LSP MCP Tools
+
+LeanProbe and LSP-backed Lean MCP servers are complementary. Tools such as
+`lean-lsp-mcp` are broad project-navigation and interaction layers over
+`lake serve`: they are the better fit for file-position diagnostics, goals,
+hover information, references, completions, code actions, widgets, and theorem
+search integrations.
+
+LeanProbe is narrower: it screens complete declaration replacements against a
+cached LeanInteract environment, exposes proof-state stepping for standalone
+snippets, and benchmarks declaration-level agent loops against `lake env lean`.
+Use it when an agent is trying many candidate declarations or moving through a
+file in source order. Use an LSP MCP beside it when the agent needs editor-like
+semantic context around the file.
+
 ## Install
 
 LeanProbe is a Python package that talks to Lean through LeanInteract. `pip`
@@ -144,7 +160,7 @@ Check the Python package and CLI:
 
 ```bash
 python -c "import lean_probe, lean_interact; print('ok')"
-lean-probe --version  # lean-probe 0.2.0
+lean-probe --version  # lean-probe 0.2.2
 ```
 
 Check that Lean/Lake are visible:
@@ -185,6 +201,8 @@ repository with `python -m pytest -q`.
 ```bash
 lean-probe prepare /path/to/File.lean --cwd /path/to/lake-project --theorem-id my_theorem
 
+lean-probe capabilities --cwd /path/to/lake-project --pretty
+
 lean-probe check /path/to/File.lean my_theorem \
   --cwd /path/to/lake-project \
   --replacement-file /tmp/candidate.lean \
@@ -280,14 +298,20 @@ Example MCP configuration with LeanProbe environment variables:
       "args": ["mcp"],
       "env": {
         "LEAN_PROBE_LAKE_PATH": "/opt/homebrew/bin/lake",
-        "LEAN_PROBE_AUTO_BUILD": "1"
+        "LEAN_PROBE_AUTO_BUILD": "0"
       }
     }
   }
 }
 ```
 
-Use `lean_probe_prepare` before repeated checks in the same file, then call
+For stdio MCP clients such as Codex, keep `LEAN_PROBE_AUTO_BUILD=0` and build
+the Lean project from a terminal before using LeanProbe. Some Lean/Lake build
+commands print progress to stdout; stdout is reserved for MCP JSON-RPC frames,
+so build output can corrupt the transport.
+
+Use `lean_probe_capabilities` when setup is uncertain. Use
+`lean_probe_prepare` before repeated checks in the same file, then call
 `lean_probe_check` for concrete target declarations or replacements. When
 ordinary diagnostics are not enough, call `lean_probe_feedback` and inspect
 `messages`, `tactics`, and `feedback_lean`. See [AGENT.md](AGENT.md) for the

{lean_probe-0.2.0 → lean_probe-0.2.2}/README.md

@@ -15,8 +15,9 @@ acceptance.
 ## MCP Tools
 
 LeanProbe exposes the MCP server name `lean-probe` and the tools
-`lean_probe_prepare`, `lean_probe_check`, `lean_probe_feedback`,
-`lean_probe_state`, `lean_probe_step`, and `lean_probe_close_state`.
+`lean_probe_capabilities`, `lean_probe_prepare`, `lean_probe_check`,
+`lean_probe_feedback`, `lean_probe_state`, `lean_probe_step`, and
+`lean_probe_close_state`.
 
 For MCP parameter details, result-field semantics, and `feedback_lean` examples,
 see [AGENT.md](AGENT.md).
@@ -59,6 +60,21 @@ The benchmark suite measures two cases:
 - sequential same-file checks: prepare a header once, then advance declaration by
   declaration with env reuse.
 
+## How It Differs From LSP MCP Tools
+
+LeanProbe and LSP-backed Lean MCP servers are complementary. Tools such as
+`lean-lsp-mcp` are broad project-navigation and interaction layers over
+`lake serve`: they are the better fit for file-position diagnostics, goals,
+hover information, references, completions, code actions, widgets, and theorem
+search integrations.
+
+LeanProbe is narrower: it screens complete declaration replacements against a
+cached LeanInteract environment, exposes proof-state stepping for standalone
+snippets, and benchmarks declaration-level agent loops against `lake env lean`.
+Use it when an agent is trying many candidate declarations or moving through a
+file in source order. Use an LSP MCP beside it when the agent needs editor-like
+semantic context around the file.
+
 ## Install
 
 LeanProbe is a Python package that talks to Lean through LeanInteract. `pip`
@@ -107,7 +123,7 @@ Check the Python package and CLI:
 
 ```bash
 python -c "import lean_probe, lean_interact; print('ok')"
-lean-probe --version  # lean-probe 0.2.0
+lean-probe --version  # lean-probe 0.2.2
 ```
 
 Check that Lean/Lake are visible:
@@ -148,6 +164,8 @@ repository with `python -m pytest -q`.
 ```bash
 lean-probe prepare /path/to/File.lean --cwd /path/to/lake-project --theorem-id my_theorem
 
+lean-probe capabilities --cwd /path/to/lake-project --pretty
+
 lean-probe check /path/to/File.lean my_theorem \
   --cwd /path/to/lake-project \
   --replacement-file /tmp/candidate.lean \
@@ -243,14 +261,20 @@ Example MCP configuration with LeanProbe environment variables:
       "args": ["mcp"],
       "env": {
         "LEAN_PROBE_LAKE_PATH": "/opt/homebrew/bin/lake",
-        "LEAN_PROBE_AUTO_BUILD": "1"
+        "LEAN_PROBE_AUTO_BUILD": "0"
       }
     }
   }
 }
 ```
 
-Use `lean_probe_prepare` before repeated checks in the same file, then call
+For stdio MCP clients such as Codex, keep `LEAN_PROBE_AUTO_BUILD=0` and build
+the Lean project from a terminal before using LeanProbe. Some Lean/Lake build
+commands print progress to stdout; stdout is reserved for MCP JSON-RPC frames,
+so build output can corrupt the transport.
+
+Use `lean_probe_capabilities` when setup is uncertain. Use
+`lean_probe_prepare` before repeated checks in the same file, then call
 `lean_probe_check` for concrete target declarations or replacements. When
 ordinary diagnostics are not enough, call `lean_probe_feedback` and inspect
 `messages`, `tactics`, and `feedback_lean`. See [AGENT.md](AGENT.md) for the

{lean_probe-0.2.0 → lean_probe-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "lean-probe"
-version = "0.2.0"
+version = "0.2.2"
 description = "Fast Lean 4 proof feedback for agents, powered by LeanInteract."
 readme = "README.md"
 requires-python = ">=3.10"

{lean_probe-0.2.0 → lean_probe-0.2.2}/src/lean_probe/cli.py

@@ -64,6 +64,8 @@ def build_parser() -> argparse.ArgumentParser:
     common_parent.add_argument("--verbose", action="store_true", help="Enable LeanInteract verbose setup")
     common_parent.add_argument("--pretty", action="store_true", help="Pretty-print JSON")
 
+    sub.add_parser("capabilities", parents=[common_parent], help="Report LeanProbe readiness and live sessions")
+
     prepare = sub.add_parser("prepare", parents=[common_parent], help="Warm imports and optional prior declarations")
     prepare.add_argument("file_path")
     prepare.add_argument("--theorem-id", default="")
@@ -249,7 +251,9 @@ def main(argv: list[str] | None = None) -> int:
 
     probe = _probe_from_args(args)
     try:
-        if args.command == "prepare":
+        if args.command == "capabilities":
+            payload = probe.capabilities(cwd=args.cwd or None)
+        elif args.command == "prepare":
             payload = probe.prepare_file(
                 args.file_path,
                 theorem_id=args.theorem_id,
@@ -305,6 +309,8 @@ def main(argv: list[str] | None = None) -> int:
         probe.close()
 
     _emit(payload, pretty=bool(getattr(args, "pretty", False)))
+    if args.command == "capabilities":
+        return 0 if payload.get("available") else 1
     return 0 if payload.get("success") else 1
 
 

{lean_probe-0.2.0 → lean_probe-0.2.2}/src/lean_probe/mcp_server.py

@@ -25,6 +25,7 @@ def ParamField(*, description: str) -> Any:
 
 MCP_SERVER_NAME = "lean-probe"
 TOOL_NAMES = [
+    "lean_probe_capabilities",
     "lean_probe_prepare",
     "lean_probe_check",
     "lean_probe_feedback",
@@ -105,6 +106,19 @@ def create_server(probe: LeanProbe | None = None) -> Any:
     active_probe = probe or _probe_from_env()
     mcp = FastMCP(MCP_SERVER_NAME)
 
+    @mcp.tool()
+    def lean_probe_capabilities(
+        cwd: Cwd = "",
+    ) -> dict[str, Any]:
+        """Report LeanProbe readiness, selected project root/REPL, and live sessions.
+
+        Use this first when setup is uncertain. `available=false` means the
+        response includes `degraded_codes` and `degraded_reasons` describing
+        missing LeanInteract support, project-root detection, or REPL setup.
+        """
+
+        return active_probe.capabilities(cwd=cwd or None)
+
     @mcp.tool()
     def lean_probe_prepare(
         file_path: FilePath,

{lean_probe-0.2.0 → lean_probe-0.2.2/src/lean_probe.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lean-probe
-Version: 0.2.0
+Version: 0.2.2
 Summary: Fast Lean 4 proof feedback for agents, powered by LeanInteract.
 Author: LeanProbe contributors
 License-Expression: MIT
@@ -52,8 +52,9 @@ acceptance.
 ## MCP Tools
 
 LeanProbe exposes the MCP server name `lean-probe` and the tools
-`lean_probe_prepare`, `lean_probe_check`, `lean_probe_feedback`,
-`lean_probe_state`, `lean_probe_step`, and `lean_probe_close_state`.
+`lean_probe_capabilities`, `lean_probe_prepare`, `lean_probe_check`,
+`lean_probe_feedback`, `lean_probe_state`, `lean_probe_step`, and
+`lean_probe_close_state`.
 
 For MCP parameter details, result-field semantics, and `feedback_lean` examples,
 see [AGENT.md](AGENT.md).
@@ -96,6 +97,21 @@ The benchmark suite measures two cases:
 - sequential same-file checks: prepare a header once, then advance declaration by
   declaration with env reuse.
 
+## How It Differs From LSP MCP Tools
+
+LeanProbe and LSP-backed Lean MCP servers are complementary. Tools such as
+`lean-lsp-mcp` are broad project-navigation and interaction layers over
+`lake serve`: they are the better fit for file-position diagnostics, goals,
+hover information, references, completions, code actions, widgets, and theorem
+search integrations.
+
+LeanProbe is narrower: it screens complete declaration replacements against a
+cached LeanInteract environment, exposes proof-state stepping for standalone
+snippets, and benchmarks declaration-level agent loops against `lake env lean`.
+Use it when an agent is trying many candidate declarations or moving through a
+file in source order. Use an LSP MCP beside it when the agent needs editor-like
+semantic context around the file.
+
 ## Install
 
 LeanProbe is a Python package that talks to Lean through LeanInteract. `pip`
@@ -144,7 +160,7 @@ Check the Python package and CLI:
 
 ```bash
 python -c "import lean_probe, lean_interact; print('ok')"
-lean-probe --version  # lean-probe 0.2.0
+lean-probe --version  # lean-probe 0.2.2
 ```
 
 Check that Lean/Lake are visible:
@@ -185,6 +201,8 @@ repository with `python -m pytest -q`.
 ```bash
 lean-probe prepare /path/to/File.lean --cwd /path/to/lake-project --theorem-id my_theorem
 
+lean-probe capabilities --cwd /path/to/lake-project --pretty
+
 lean-probe check /path/to/File.lean my_theorem \
   --cwd /path/to/lake-project \
   --replacement-file /tmp/candidate.lean \
@@ -280,14 +298,20 @@ Example MCP configuration with LeanProbe environment variables:
       "args": ["mcp"],
       "env": {
         "LEAN_PROBE_LAKE_PATH": "/opt/homebrew/bin/lake",
-        "LEAN_PROBE_AUTO_BUILD": "1"
+        "LEAN_PROBE_AUTO_BUILD": "0"
       }
     }
   }
 }
 ```
 
-Use `lean_probe_prepare` before repeated checks in the same file, then call
+For stdio MCP clients such as Codex, keep `LEAN_PROBE_AUTO_BUILD=0` and build
+the Lean project from a terminal before using LeanProbe. Some Lean/Lake build
+commands print progress to stdout; stdout is reserved for MCP JSON-RPC frames,
+so build output can corrupt the transport.
+
+Use `lean_probe_capabilities` when setup is uncertain. Use
+`lean_probe_prepare` before repeated checks in the same file, then call
 `lean_probe_check` for concrete target declarations or replacements. When
 ordinary diagnostics are not enough, call `lean_probe_feedback` and inspect
 `messages`, `tactics`, and `feedback_lean`. See [AGENT.md](AGENT.md) for the

{lean_probe-0.2.0 → lean_probe-0.2.2}/tests/test_cli.py

@@ -101,6 +101,21 @@ def test_cli_check_outputs_json(monkeypatch, tmp_path, capsys):
     assert output["target"] == "demo"
 
 
+def test_cli_capabilities_outputs_readiness(monkeypatch, tmp_path, capsys):
+    _install_fake_lean_interact(monkeypatch)
+    project = tmp_path / "Demo"
+    project.mkdir()
+    (project / "lakefile.lean").write_text("import Lake\n", encoding="utf-8")
+
+    code = cli.main(["capabilities", "--cwd", str(project)])
+    output = json.loads(capsys.readouterr().out)
+
+    assert code == 0
+    assert output["available"] is True
+    assert output["project_root"] == str(project)
+    assert output["degraded_codes"] == []
+
+
 def test_cli_prepare_and_feedback_pretty(monkeypatch, tmp_path, capsys):
     _install_fake_lean_interact(monkeypatch)
     project = tmp_path / "Demo"

{lean_probe-0.2.0 → lean_probe-0.2.2}/tests/test_mcp_server.py

@@ -9,6 +9,9 @@ class _FakeProbe:
     def __init__(self):
         self.closed = False
 
+    def capabilities(self, *args, **kwargs):
+        return {"action": "capabilities", "args": args, "kwargs": kwargs}
+
     def prepare_file(self, *args, **kwargs):
         return {"action": "prepare", "args": args, "kwargs": kwargs}
 
@@ -34,6 +37,7 @@ class _FakeProbe:
 def test_mcp_public_names_are_stable():
     assert MCP_SERVER_NAME == "lean-probe"
     assert TOOL_NAMES == [
+        "lean_probe_capabilities",
         "lean_probe_prepare",
         "lean_probe_check",
         "lean_probe_feedback",
@@ -52,6 +56,8 @@ def test_mcp_tool_descriptions_expose_agent_contracts():
     server = create_server(probe=_FakeProbe())
     tools = server._tool_manager._tools
 
+    assert "readiness" in tools["lean_probe_capabilities"].description
+    assert "degraded_codes" in tools["lean_probe_capabilities"].description
     assert "cached only inside this running MCP server process" in tools["lean_probe_prepare"].description
     assert "complete declaration chunk" in tools["lean_probe_check"].description
     assert "success=false" in tools["lean_probe_check"].description
@@ -72,6 +78,7 @@ def test_mcp_tool_wrappers_call_injected_probe():
     server = create_server(probe=_FakeProbe())
     tools = server._tool_manager._tools
 
+    capabilities = tools["lean_probe_capabilities"].fn(cwd="/tmp/project")
     check = tools["lean_probe_check"].fn(
         file_path="Demo.lean",
         theorem_id="demo",
@@ -83,6 +90,8 @@ def test_mcp_tool_wrappers_call_injected_probe():
     step = tools["lean_probe_step"].fn(session_id="session", proof_state=3, tactic="rfl", timeout_s=5)
     close = tools["lean_probe_close_state"].fn(session_id="session")
 
+    assert capabilities["action"] == "capabilities"
+    assert capabilities["kwargs"]["cwd"] == "/tmp/project"
     assert check["action"] == "check"
     assert check["kwargs"]["cwd"] == "/tmp/project"
     assert check["kwargs"]["include_tactics"] is True