Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
feature/Sdk-monorepo-consumer-links · L-261002-69b215 (#1317)
Louis Choquel7e8ea4d15213
diff --git a/.claude/skills/bump-kajson/SKILL.md b/.claude/skills/bump-kajson/SKILL.mdindex 64bb2fbb6..b850c7c5a 100644--- a/.claude/skills/bump-kajson/SKILL.md+++ b/.claude/skills/bump-kajson/SKILL.md@@ -78,8 +78,8 @@ even when the release carries nothing this engine uses.## The cascade is narrow — say so rather than hunting for it`pipelex/` is the only repo in this workspace that names kajson in a-`pyproject.toml`. Everyone else — `pipelex-sdk-python`, every `pipelex-server`-member, every user install — receives kajson **transitively, through this exact+`pyproject.toml`. Everyone else — the Python SDK in `pipelex-sdk/python/`, every+`pipelex-server` member, every user install — receives kajson **transitively, through this exactpin**. Confirm it rather than trusting this sentence, because a new directdependent would change the conclusion:diff --git a/.claude/skills/bump-mthds/SKILL.md b/.claude/skills/bump-mthds/SKILL.mdindex 405fff73c..3a2d67066 100644--- a/.claude/skills/bump-mthds/SKILL.md+++ b/.claude/skills/bump-mthds/SKILL.md@@ -65,8 +65,8 @@ tests against the version it demands, with no gap for a consumer to fall into.**The standing policy is to move the pin to the latest release, every time**,even when the new release carries nothing this engine uses. The cost is real and-worth naming when you report: everyone downstream — `pipelex-sdk-python`,-`pipelex-server`, every user install — is forced onto that exact `mthds`, and a+worth naming when you report: everyone downstream — the Python SDK in+`pipelex-sdk/python/`, `pipelex-server`, every user install — is forced onto that exact `mthds`, and aconsumer that also depends on `mthds` directly must now move in step withpipelex rather than resolving its own. Say so in the changelog when the bump isotherwise uneventful, because for a consumer "pipelex now requires mthds@@ -120,7 +120,7 @@ ledger list --origin mthds-python --status openThe second query is the targeted one — every item `mthds-python` filed, whereverit landed — and it is worth reading past the rows owned by this repo, because a-row owned by `pipelex-sdk-python` or by `mthds` is a piece of the same cascade+row owned by `pipelex-sdk` or by `mthds` is a piece of the same cascadeyou will be filing into at step 10.An item that describes the adaptation you are about to do should be claimed@@ -330,14 +330,16 @@ ones harder to spot.changed, and the check that went green. `Closes <id>` goes in the PR body whenthe user opens one.- **File the cascade, and note that the exact pin makes it sharper.**- `pipelex-sdk-python` pins `mthds` exactly too, and `pipelex-server` pins- `pipelex` exactly at several sites — so any bump here, breaking or not, puts- a consumer that installs both this package and `pipelex-sdk-python` into an- unsatisfiable resolve until that repo moves to the same version. Check where- it stands (`grep mthds ../pipelex-sdk-python/pyproject.toml`) and say so in- your report. Neither repo is yours to edit from here: file it- (`ledger new --owner <repo> …`) with the version that moved and, when there- was one, the symbol. The `ledger` skill has the full gesture.+ The Python SDK in `pipelex-sdk/python/` pins `mthds` exactly too, and+ `pipelex-server` pins `pipelex` exactly at several sites — so any bump here,+ breaking or not, puts a consumer that installs both this package and the+ `pipelex-sdk` distribution into an unsatisfiable resolve until `pipelex-sdk`+ moves to the same version. Check where it stands+ (`grep mthds ../pipelex-sdk/python/pyproject.toml`) and say so in your report.+ Neither repo is yours to edit from here: file it against the member that+ holds the pin (`ledger new --owner pipelex-sdk/python …`, and+ `--owner pipelex-server/<member>` for a server pin) with the version that+ moved and, when there was one, the symbol. The `ledger` skill has the full gesture.- **File the reverse direction if you moved the wire.** `mthds-python` commitsprotocol parity fixtures captured *from this engine*, so a change here thatalters emitted output means those fixtures need recapturing — an item owned bydiff --git a/CHANGELOG.md b/CHANGELOG.mdindex 5cfeebe12..f8640c808 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -1,5 +1,11 @@# Changelog+## [Unreleased]++### Changed++- **The method-app template and the SDK references link `Pipelex/pipelex-sdk`**: the SDKs and the method-app templates now live in the `Pipelex/pipelex-sdk` repository, so the README and the documentation's **Quick Start** link the method-app template to its `method-apps/` directory, the webapp's by-hand commands clone it and copy `method-apps/webapp-js/`, and the `@pipelex/sdk` and `pipelex-sdk` references point at its `js/docs/` and `python/docs/` directories.+## [v0.71.1] - 2026-10-01### Fixeddiff --git a/README.md b/README.mdindex e4b9be237..6f2665e28 100644--- a/README.md+++ b/README.md@@ -77,7 +77,7 @@ You get a run id straight away, and you can ask for its status, its results or tGive the file as a URL the Pipelex MCP can reach. In ChatGPT you can attach it to the conversation instead and ask for a run on it; Claude has no way yet to hand the Pipelex MCP a file you attached.-**The other two ways, built by your agent too.** Ask it for a webapp around the method, and `/pipelex-scaffold` creates a new app from the [method-app template](https://github.com/Pipelex/pipelex-method-apps) and leaves it running on your machine. Ask it to call the method from your TypeScript or Python code, and `/pipelex-integrate` generates the method's types and one typed call that runs it, through the TypeScript SDK [`@pipelex/sdk`](https://www.npmjs.com/package/@pipelex/sdk) or the Python SDK [`pipelex-sdk`](https://pypi.org/project/pipelex-sdk/). Any other software runs a method via API through `POST /v1/start`, with any HTTP client.+**The other two ways, built by your agent too.** Ask it for a webapp around the method, and `/pipelex-scaffold` creates a new app from the [method-app template](https://github.com/Pipelex/pipelex-sdk/tree/main/method-apps) and leaves it running on your machine. Ask it to call the method from your TypeScript or Python code, and `/pipelex-integrate` generates the method's types and one typed call that runs it, through the TypeScript SDK [`@pipelex/sdk`](https://www.npmjs.com/package/@pipelex/sdk) or the Python SDK [`pipelex-sdk`](https://pypi.org/project/pipelex-sdk/). Any other software runs a method via API through `POST /v1/start`, with any HTTP client.**Next:** [what Pipelex is](https://go.pipelex.com/product) · [documentation](https://go.pipelex.com/docs) · [your console](https://app.pipelex.com) · [Discord](https://go.pipelex.com/discord)diff --git a/docs/get-started/quick-start.md b/docs/get-started/quick-start.mdindex b43a7fd7d..7b212dc86 100644--- a/docs/get-started/quick-start.md+++ b/docs/get-started/quick-start.md@@ -82,12 +82,12 @@ Your agent builds these too, and each can also be done by hand.### As a webapp-Ask your agent for a webapp around the method, and `/pipelex-scaffold` creates a new app from the [method-app template](https://github.com/Pipelex/pipelex-method-apps) and leaves it running on your machine. By hand, the same app takes these commands:+Ask your agent for a webapp around the method, and `/pipelex-scaffold` creates a new app from the [method-app template](https://github.com/Pipelex/pipelex-sdk/tree/main/method-apps) and leaves it running on your machine. By hand, the same app takes these commands:```bashsrc=$(mktemp -d)-git clone --depth 1 https://github.com/Pipelex/pipelex-method-apps.git "$src"-mkdir -p my-app && cp -R "$src/webapp-js/." my-app/+git clone --depth 1 https://github.com/Pipelex/pipelex-sdk.git "$src"+mkdir -p my-app && cp -R "$src/method-apps/webapp-js/." my-app/cd my-app && git initexport PIPELEX_API_KEY=plx_sk_...@@ -147,7 +147,7 @@ export PIPELEX_API_KEY=plx_sk_...console.log(result.main_stuff);```- More in the [`@pipelex/sdk` reference](https://github.com/Pipelex/pipelex-sdk-js/tree/main/docs).+ More in the [`@pipelex/sdk` reference](https://github.com/Pipelex/pipelex-sdk/tree/main/js/docs).=== "Python"@@ -178,7 +178,7 @@ export PIPELEX_API_KEY=plx_sk_...asyncio.run(main())```- More in the [`pipelex-sdk` reference](https://github.com/Pipelex/pipelex-sdk-python/tree/main/docs).+ More in the [`pipelex-sdk` reference](https://github.com/Pipelex/pipelex-sdk/tree/main/python/docs).**Next:** [what Pipelex is](https://go.pipelex.com/product) · [documentation](https://go.pipelex.com/docs) · [your console](https://app.pipelex.com) · [Discord](https://go.pipelex.com/discord)