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.
Merge remote-tracking branch 'origin/main' into dev
Louis Choquel2c856785f470
diff --cc CHANGELOG.mdindex 6c810d182,c321186a5..1481a7ff0--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -1,7 -1,7 +1,12 @@@# Changelog+## [Unreleased]+++- **The README leads with the hosted route**: its quick start is the onboarding region included from `Pipelex/.github` — sign up at app.pipelex.com, then the Pipelex plugin in Claude Code or Codex or the Pipelex MCP in ChatGPT or Claude — and the runtime's own install, configuration and first run follow under their own heading, **Run it yourself**. The CV batch screening walkthrough moved from the README to the cookbook in the documentation. Its hero is the website's line, "Turn your expertise into an AI-powered App, MCP or API", with a paragraph on building a method with your coding agent and where it runs, and **What a method looks like** and **Why methods?** follow the install instead of preceding it.++- **`mthds` version**: The pin moves to `mthds==0.16.0`, the release adding a `User-Agent` on every `MthdsAPIClient` request and the `mthds.version` module. Nothing in pipelex uses either, and the MTHDS standard version stays at `2.0.0`, but the pin is exact, so everyone downstream inherits `mthds` 0.16.0 and a consumer depending on `mthds` directly must move in step.+++ ## [v0.64.0] - 2026-09-24+### Added- **A caller can be known without a run**: `CallerIdentity` (`pipelex.system.caller_identity`) holds the `user_id` and `extras` a host would state on a run, and `scoped_caller_identity` makes one the ambient caller for a block. An event emitted with no `RunMetadata` in hand reads the caller in scope before it falls back to the configured `user_id`, and `PipelexMTHDSProtocol.caller_identity` exposes the caller a protocol was built for.