Repository navigation
[chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs - #7252
Conversation
OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29:
$2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic
coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor
of the pinned 0.87.1) carries it on the openai, azure, and openai-codex
providers and makes it the Codex default.
- Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai
alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin,
and the provider-cost patch spec (new CLI chunk hash; both anchors
verified to bind exactly once in 0.99.1).
- Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555
models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the
openrouter variants, and anthropic/claude-sonnet-5-5).
- Retire the Sonnet 5.5 curated addition and its runner-side
registration entry; pi 0.99.1 carries the model itself.
- Add gpt-6.1-sol to supported_llm_models["openai"],
PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the
API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new
Codex default), plus curated overlay labels/descriptions/ratings.
- Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in
the pi-ai catalog).
- Mirror Pi 0.99's bash-tool change in the in-process engine: a
non-zero exit returns an isError result instead of throwing.
Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is
rejected by the ChatGPT backend for gpt-6.1-sol ("model is not
supported when using Codex with a ChatGPT account", verified live);
Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x
major bump, tracked separately. CODEX_MODELS is unchanged.
Cost tracking needs no code change: the API prices spans from litellm's
live price map, which already carries gpt-6.1-sol (verified:
resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to
$0.010062/$0.0001, matching Pi's billed numbers).
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
📝 SummarySummary by CodeRabbit
WalkthroughPi is updated to version 0.99.1. Model catalogs and provider lists add GPT-6.1 Sol, and the Together AI default changes to Kimi-K3. The Bash tool now returns non-zero command exits as error-marked results. ChangesPi runtime and model behavior
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: 🔵 Low · up to The Together AI prompt model list can omit the new Kimi-K3 default. Align that list with the default catalog; otherwise the change is mergeable with awareness of this bounded inconsistency. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The inspected changes preserve existing authorization checks and keep command failures visible. No introduced security issue was established, but incomplete dependency and rollout coverage leaves residual uncertainty. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 60.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 15 files. (4 skipped: 4 unsupported.)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Advanced
Run ID: 6d24a845-94b1-458f-b16c-b4b56c97d3f1
⛔ Files ignored due to path filters (2)
sdks/python/agenta/sdk/agents/data/pi_models.generated.jsonis excluded by!**/*.generated.*services/runner/pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (19)
api/oss/src/core/secrets/enums.pyapi/oss/tests/pytest/unit/secrets/test_subscription_provider.pyapi/oss/tests/pytest/unit/vault/test_subscription_login_routes.pysdks/python/agenta/sdk/agents/capabilities.pysdks/python/agenta/sdk/agents/data/pi_models.curated.jsonsdks/python/agenta/sdk/utils/assets.pysdks/python/oss/tests/pytest/unit/agents/connections/test_capabilities.pysdks/python/oss/tests/pytest/unit/agents/connections/test_model_catalog.pyservices/runner/images/sandbox/daytona/README.mdservices/runner/images/sandbox/daytona/build_snapshot.pyservices/runner/package.jsonservices/runner/src/engines/inprocess/tools/bash-tool.tsservices/runner/src/engines/sandbox_agent/daytona.tsservices/runner/src/engines/sandbox_agent/pi-model-config.tsservices/runner/src/tools/pi-provider-cost-patch.jsonservices/runner/src/tools/pi-provider-cost-patch.tsservices/runner/src/tools/pi-validation-patch.tsservices/runner/tests/unit/inprocess/bash-tool.test.tsservices/runner/tests/unit/sandbox-agent-pi-model-registration.test.ts
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.
Railway Preview Environment
PR closed or converted to draft. Environment absence verified; retained storage requires separate provider accounting. Post |
…mi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place.
* feat(channels): inbound files on Slack, Telegram, and WhatsApp voice/video Pass inbound files to the agent as session attachments on every channel, reusing the WhatsApp media path: - WhatsApp: audio (voice notes) and video join image and document as media parts; only stickers, locations, and contact cards keep the fixed reply. - Telegram: photo, document, voice, audio, video, and video_note become media parts; fetch_media downloads through getFile with the bot token (deployment token on the hosted path); files.receive capability on at the Bot API's 20 MB cap. - Slack: each entry of a message's files array becomes a media part; fetch_media downloads url_private_download with the bot token and refuses an HTML login-page response. Attachment delivery downstream is unchanged: native images are inlined into the model prompt where supported, everything else lands as a file in the session working directory. OpenSpec change: channel-inbound-media. * refactor(channels): resolve Slack files at download time; one Telegram token hook Codex review follow-up on the inbound-media commit: - Slack stores only the file id on the inbox event; fetch_media resolves the current size and private URL through files.info at download time, so no private URL or size is persisted in channel_inbox_events. The mapping moves to slack/mapping.py next to the other pure mapping code, and a file-only share no longer carries an empty text part. - Telegram: one _api_token hook replaces _media_token; the base _call and fetch_media both read it, and the hosted adapter's _call override is deleted (it only swapped the token). - Telegram photo selection picks the largest size by area (file_size as tiebreaker) instead of trusting list order. - Tests: files.info resolution, no-URL refusal, file-only share shape, hosted deployment-token download, unordered photo sizes, and explicit project-scoping assertions on the dispatcher attachment path. - OpenSpec wording matches the code; README gains the change entry. * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(channels): keep the Telegram token out of download errors; name unnamed files A failed Telegram file download raised httpx's HTTPStatusError, whose message carries the request URL. That URL holds the bot token, and the inbox dispatcher logs the message, so a file that failed to download put a working token in the logs. Raise a status-only error instead. Files a platform sends without a name (Telegram photos, voice notes, video notes; WhatsApp images and voice notes) were stored as `image`, `audio`, or `video` with no extension. Name them `<kind>-<send time>.<ext>` from the message's send time and the detected type, so a retried dispatch keeps the same name. The spec now states that the platform attachment limit, not each channel's advertised max_bytes, is the effective cap. * fix(deps): update hono to 4.13.5 (#7249) * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(deps): update hono to 4.13.5 --------- Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update fast-uri to 3.1.7 (#7245) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs (#7252) * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor of the pinned 0.87.1) carries it on the openai, azure, and openai-codex providers and makes it the Codex default. - Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin, and the provider-cost patch spec (new CLI chunk hash; both anchors verified to bind exactly once in 0.99.1). - Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555 models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the openrouter variants, and anthropic/claude-sonnet-5-5). - Retire the Sonnet 5.5 curated addition and its runner-side registration entry; pi 0.99.1 carries the model itself. - Add gpt-6.1-sol to supported_llm_models["openai"], PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new Codex default), plus curated overlay labels/descriptions/ratings. - Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in the pi-ai catalog). - Mirror Pi 0.99's bash-tool change in the in-process engine: a non-zero exit returns an isError result instead of throwing. Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for gpt-6.1-sol ("model is not supported when using Codex with a ChatGPT account", verified live); Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x major bump, tracked separately. CODEX_MODELS is unchanged. Cost tracking needs no code change: the API prices spans from litellm's live price map, which already carries gpt-6.1-sol (verified: resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to $0.010062/$0.0001, matching Pi's billed numbers). * fix(sdk): replace retired Together AI Kimi K2.6 and K2.7-Code with Kimi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place. * chore(deps): bump undici from 8.10.0 to 8.10.2 in /services/runner (#7230) Bumps [undici](https://github.com/nodejs/undici) from 8.10.0 to 8.10.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v8.10.0...v8.10.2) --- updated-dependencies: - dependency-name: undici dependency-version: 8.10.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(deps): update image-size to 2.0.3 (#7246) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update mermaid to 11.16.1 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Agenta Product Agent <agent@agenta.ai> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* feat(channels): inbound files on Slack, Telegram, and WhatsApp voice/video Pass inbound files to the agent as session attachments on every channel, reusing the WhatsApp media path: - WhatsApp: audio (voice notes) and video join image and document as media parts; only stickers, locations, and contact cards keep the fixed reply. - Telegram: photo, document, voice, audio, video, and video_note become media parts; fetch_media downloads through getFile with the bot token (deployment token on the hosted path); files.receive capability on at the Bot API's 20 MB cap. - Slack: each entry of a message's files array becomes a media part; fetch_media downloads url_private_download with the bot token and refuses an HTML login-page response. Attachment delivery downstream is unchanged: native images are inlined into the model prompt where supported, everything else lands as a file in the session working directory. OpenSpec change: channel-inbound-media. * refactor(channels): resolve Slack files at download time; one Telegram token hook Codex review follow-up on the inbound-media commit: - Slack stores only the file id on the inbox event; fetch_media resolves the current size and private URL through files.info at download time, so no private URL or size is persisted in channel_inbox_events. The mapping moves to slack/mapping.py next to the other pure mapping code, and a file-only share no longer carries an empty text part. - Telegram: one _api_token hook replaces _media_token; the base _call and fetch_media both read it, and the hosted adapter's _call override is deleted (it only swapped the token). - Telegram photo selection picks the largest size by area (file_size as tiebreaker) instead of trusting list order. - Tests: files.info resolution, no-URL refusal, file-only share shape, hosted deployment-token download, unordered photo sizes, and explicit project-scoping assertions on the dispatcher attachment path. - OpenSpec wording matches the code; README gains the change entry. * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(channels): keep the Telegram token out of download errors; name unnamed files A failed Telegram file download raised httpx's HTTPStatusError, whose message carries the request URL. That URL holds the bot token, and the inbox dispatcher logs the message, so a file that failed to download put a working token in the logs. Raise a status-only error instead. Files a platform sends without a name (Telegram photos, voice notes, video notes; WhatsApp images and voice notes) were stored as `image`, `audio`, or `video` with no extension. Name them `<kind>-<send time>.<ext>` from the message's send time and the detected type, so a retried dispatch keeps the same name. The spec now states that the platform attachment limit, not each channel's advertised max_bytes, is the effective cap. * fix(deps): update hono to 4.13.5 (#7249) * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(deps): update hono to 4.13.5 --------- Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update fast-uri to 3.1.7 (#7245) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs (#7252) * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor of the pinned 0.87.1) carries it on the openai, azure, and openai-codex providers and makes it the Codex default. - Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin, and the provider-cost patch spec (new CLI chunk hash; both anchors verified to bind exactly once in 0.99.1). - Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555 models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the openrouter variants, and anthropic/claude-sonnet-5-5). - Retire the Sonnet 5.5 curated addition and its runner-side registration entry; pi 0.99.1 carries the model itself. - Add gpt-6.1-sol to supported_llm_models["openai"], PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new Codex default), plus curated overlay labels/descriptions/ratings. - Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in the pi-ai catalog). - Mirror Pi 0.99's bash-tool change in the in-process engine: a non-zero exit returns an isError result instead of throwing. Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for gpt-6.1-sol ("model is not supported when using Codex with a ChatGPT account", verified live); Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x major bump, tracked separately. CODEX_MODELS is unchanged. Cost tracking needs no code change: the API prices spans from litellm's live price map, which already carries gpt-6.1-sol (verified: resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to $0.010062/$0.0001, matching Pi's billed numbers). * fix(sdk): replace retired Together AI Kimi K2.6 and K2.7-Code with Kimi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place. * chore(deps): bump undici from 8.10.0 to 8.10.2 in /services/runner (#7230) Bumps [undici](https://github.com/nodejs/undici) from 8.10.0 to 8.10.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v8.10.0...v8.10.2) --- updated-dependencies: - dependency-name: undici dependency-version: 8.10.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(deps): update image-size to 2.0.3 (#7246) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update mermaid to 11.16.1 (#7253) * feat(channels): inbound files on Slack, Telegram, and WhatsApp voice/video Pass inbound files to the agent as session attachments on every channel, reusing the WhatsApp media path: - WhatsApp: audio (voice notes) and video join image and document as media parts; only stickers, locations, and contact cards keep the fixed reply. - Telegram: photo, document, voice, audio, video, and video_note become media parts; fetch_media downloads through getFile with the bot token (deployment token on the hosted path); files.receive capability on at the Bot API's 20 MB cap. - Slack: each entry of a message's files array becomes a media part; fetch_media downloads url_private_download with the bot token and refuses an HTML login-page response. Attachment delivery downstream is unchanged: native images are inlined into the model prompt where supported, everything else lands as a file in the session working directory. OpenSpec change: channel-inbound-media. * refactor(channels): resolve Slack files at download time; one Telegram token hook Codex review follow-up on the inbound-media commit: - Slack stores only the file id on the inbox event; fetch_media resolves the current size and private URL through files.info at download time, so no private URL or size is persisted in channel_inbox_events. The mapping moves to slack/mapping.py next to the other pure mapping code, and a file-only share no longer carries an empty text part. - Telegram: one _api_token hook replaces _media_token; the base _call and fetch_media both read it, and the hosted adapter's _call override is deleted (it only swapped the token). - Telegram photo selection picks the largest size by area (file_size as tiebreaker) instead of trusting list order. - Tests: files.info resolution, no-URL refusal, file-only share shape, hosted deployment-token download, unordered photo sizes, and explicit project-scoping assertions on the dispatcher attachment path. - OpenSpec wording matches the code; README gains the change entry. * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(channels): keep the Telegram token out of download errors; name unnamed files A failed Telegram file download raised httpx's HTTPStatusError, whose message carries the request URL. That URL holds the bot token, and the inbox dispatcher logs the message, so a file that failed to download put a working token in the logs. Raise a status-only error instead. Files a platform sends without a name (Telegram photos, voice notes, video notes; WhatsApp images and voice notes) were stored as `image`, `audio`, or `video` with no extension. Name them `<kind>-<send time>.<ext>` from the message's send time and the detected type, so a retried dispatch keeps the same name. The spec now states that the platform attachment limit, not each channel's advertised max_bytes, is the effective cap. * fix(deps): update hono to 4.13.5 (#7249) * docs(changelog): Configure permissions for your agent * v0.121.7 * docs(changelog): new-models-and-cost-tracking (#7271) * docs(changelog): docs-on-wide-screens (#7277) * fix(chart): render the sandbox provider registry on the web workloads (#7189) The web entrypoint maps AGENTA_RUNNER_ENABLED_SANDBOX_PROVIDERS to the browser's NEXT_PUBLIC_AGENTA_ENABLED_SANDBOX_PROVIDERS. The chart rendered the registry on the runner, api and services only, so the browser fell back to "local", new agents were minted with sandbox.kind "local", and on a daytona-only install every send failed with "sandbox 'local' is not enabled on this deployment". Seen on GKE staging on 2026-09-27. The web and web-mobile Deployments now carry both registry variables through agenta.webOptionalEnv, from the same agentRunner.providers values the other workloads read. A rendered-chart test covers the default, a daytona-only install, and that the entry is rendered once. * fix(deps): update hono to 4.13.5 --------- Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update fast-uri to 3.1.7 (#7245) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs (#7252) * [chore] Add GPT-6.1 Sol: bump Pi to 0.99.1 and refresh model catalogs OpenAI released GPT-6.1 Sol (gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. Pi 0.99.1 (the direct successor of the pinned 0.87.1) carries it on the openai, azure, and openai-codex providers and makes it the Codex default. - Bump @earendil-works/pi-coding-agent and the pi-coding-agent-pi-ai alias to 0.99.1; update PINNED_PI_VERSION, the Daytona snapshot pin, and the provider-cost patch spec (new CLI chunk hash; both anchors verified to bind exactly once in 0.99.1). - Regenerate pi_models.generated.json from pi-ai 0.99.1 (541 -> 555 models; adds openai/gpt-6.1-sol, openai-codex/gpt-6.1-sol, the openrouter variants, and anthropic/claude-sonnet-5-5). - Retire the Sonnet 5.5 curated addition and its runner-side registration entry; pi 0.99.1 carries the model itself. - Add gpt-6.1-sol to supported_llm_models["openai"], PROVIDER_DEFAULT_MODELS["openai"], PI_SUBSCRIPTION_MODELS and the API's SUBSCRIPTION_PROVIDER_MODELS copy (first entry: it is Pi's new Codex default), plus curated overlay labels/descriptions/ratings. - Update the together_ai default Kimi-K2.7-Code -> Kimi-K3 (renamed in the pi-ai catalog). - Mirror Pi 0.99's bash-tool change in the in-process engine: a non-zero exit returns an isError result instead of throwing. Not in this change: the Codex harness. The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for gpt-6.1-sol ("model is not supported when using Codex with a ChatGPT account", verified live); Codex 0.159.2 accepts it, but that needs a codex-acp 1.13.1 -> 2.x major bump, tracked separately. CODEX_MODELS is unchanged. Cost tracking needs no code change: the API prices spans from litellm's live price map, which already carries gpt-6.1-sol (verified: resolve_pricing_model("gpt-6.1-sol") prices 5031/10 tokens to $0.010062/$0.0001, matching Pi's billed numbers). * fix(sdk): replace retired Together AI Kimi K2.6 and K2.7-Code with Kimi K3 Pi 0.99.1 no longer lists the two Together AI Kimi models, and litellm's pinned registry never had them, so test_model_exists_in_litellm failed. Pi now lists together_ai/moonshotai/Kimi-K3 in their place. * chore(deps): bump undici from 8.10.0 to 8.10.2 in /services/runner (#7230) Bumps [undici](https://github.com/nodejs/undici) from 8.10.0 to 8.10.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v8.10.0...v8.10.2) --- updated-dependencies: - dependency-name: undici dependency-version: 8.10.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(deps): update image-size to 2.0.3 (#7246) Co-authored-by: Depandabot Bot <dependabot@agenta.ai> * fix(deps): update mermaid to 11.16.1 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Agenta Product Agent <agent@agenta.ai> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump axios from 1.18.0 to 1.20.0 in /web/tests (#7279) * chore(deps): bump axios from 1.18.0 to 1.20.0 in /web/tests Bumps [axios](https://github.com/axios/axios) from 1.18.0 to 1.20.0. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.18.0...v1.20.0) --- updated-dependencies: - dependency-name: axios dependency-version: 1.20.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> * chore(deps): update web lockfile for axios 1.20.0 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> * fix(deps): update Pillow to 12.3.0 * fix(runner): install the sandbox lock with --no-deps so Pillow 12 can sit next to moviepy moviepy 2.2.1 (the latest) caps pillow<12, so the hash-locked install refused Pillow 12.3.0 and the runner image build failed. The lock is complete, so --no-deps installs it as written. Also lists every Pillow 12.3.0 wheel hash and drops the stale 11.3.0 ones. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Agenta Product Agent <team@agenta.ai> Co-authored-by: mmabrouk <4510758+mmabrouk@users.noreply.github.com> Co-authored-by: Agenta Product Agent <agent@agenta.ai> Co-authored-by: Depandabot Bot <dependabot@agenta.ai> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
#7252 pinned Pi 0.99.1 in the snapshot recipe but kept recipe version 1, so the runner asked for a snapshot built from the old recipe and the fingerprint test failed. Bump the version to 2, regenerate the fingerprint, and point the docs, env examples, and Helm values at agenta-agent-sandbox-v2.
Caution
Release blocker: manual QA of the ChatGPT subscription flow is required before this ships.
Pi 0.99.0 reworked ChatGPT sign-in upstream. It added a new "Sign in with ChatGPT" flow on the
openaiprovider and renamed theopenai-codexprovider that Agenta uses to "OpenAI Codex (legacy)". Our code-level and CLI checks pass (see "ChatGPT login check" below), but they do not cover the full product flow. Before the release that includes this PR, a person must run these steps on a test deployment (notoss-team) and confirm each one:ready.gpt-6.1-soland with one older model (for examplegpt-6-sol). Both complete, and the trace shows the model and a cost.readyafterward (noneeds_login).Owner: TBD. Record the result as a PR comment with the deployment and commit SHA.
ChatGPT login check (done before review)
auth.jsonfile, sameopenai-codexkey, same fields.openai-codexmodule is unchanged. The only change in that module is the interactive login's local callback server, which Agenta does not use.loginOpenAICodexDeviceCodefrom its direct@earendil-works/pi-ai@0.80.6dependency, which this PR does not change. The import resolves at runtime.gpt-6.1-solrun; the file afterward still passes the runner'svalidateSubscriptionLoginchecks.What
OpenAI released GPT-6.1 Sol (
gpt-6.1-sol) at DevDay on 2026-09-29: $2/$10 per Mtok, $0.10 cached input, 272K context, near-Astra agentic coding at one fifth of Astra's price. This adds it everywhere the platform needs it, by bumping the pinned Pi harness to 0.99.1 (the direct successor of 0.87.1 — no releases exist between them) and refreshing the catalogs.Sources: OpenAI DevDay launch, pi v0.99.1 release notes (adds GPT-6.1 Sol, makes it the Codex default, fixes
/loginwith OpenAI), litellm price map (gpt-6.1-solpresent).Changes
Runner (Pi 0.87.1 → 0.99.1)
package.json: bump@earendil-works/pi-coding-agentand thepi-coding-agent-pi-aialias to 0.99.1; lockfile regenerated.pi-provider-cost-patch.json:piVersion0.99.1, new CLI chunkopenai-completions-XW2Q5HVC.js. Both anchors verified to bind exactly once in 0.99.1 (unbundled and minified copies).PINNED_PI_VERSION(daytona.ts),PI_VERSION(build_snapshot.py), sandbox README.pi-model-config.ts: dropped the Sonnet 5.5 runner-side registration entry; pi 0.99.1 carries the model (PI_MODELS_AHEAD_OF_CATALOGis now empty).bash-tool.ts: mirror Pi 0.99's behavior change — a non-zero exit returns anisErrorresult instead of throwing (parity test updated accordingly).SDK / API catalogs
pi_models.generated.jsonregenerated from pi-ai 0.99.1 (541 → 555 models; addsopenai/gpt-6.1-sol,openai-codex/gpt-6.1-sol, openrouter variants,anthropic/claude-sonnet-5-5).pi_models.curated.json: overlay labels/descriptions/ratings for both gpt-6.1-sol ids; Sonnet 5.5 addition retired (generated entry supersedes it); sources note updated.capabilities.py:gpt-6.1-solfirst inPI_SUBSCRIPTION_MODELS["openai-codex"](it is Pi's new Codex default);openai/gpt-6.1-solinPROVIDER_DEFAULT_MODELS["openai"]; together_ai defaultKimi-K2.7-Code→Kimi-K3(renamed in the pi-ai catalog).assets.py:gpt-6.1-solinsupported_llm_models["openai"].enums.py(API):SUBSCRIPTION_PROVIDER_MODELSkept in agreement with the SDK copy.Cost tracking: no code change needed. The API prices spans from litellm's live price map, which already carries
gpt-6.1-sol. Verified through the API's own path:resolve_pricing_model("gpt-6.1-sol")resolves (bare andopenai/-prefixed) and prices 5031 input / 10 output tokens to $0.010062 / $0.0001 — matching Pi's live billed numbers below. Note: running API containers only refresh the live map at import, so the model prices correctly after the next deploy/restart.Deliberately NOT in this change: the Codex harness
The pinned Codex CLI 0.156.1 is rejected by the ChatGPT backend for this model (verified live on hetzner):
Codex CLI 0.159.2 accepts it (verified live, reply
SOL61-CODEX-NEW-OK), but wiring that in needs@agentclientprotocol/codex-acp1.13.1 → 2.x (a major) plus runner image and Daytona snapshot rebuilds — a separate change.CODEX_MODELSandcodex_models.curated.jsonare unchanged so the picker never offers an id that fails at run time.Testing (hetzner: live; local: suites)
Live on hetzner (
/data/mahmoud/sol61-test, pi 0.99.1, ChatGPT subscription login):pi --provider openai-codex --model gpt-6.1-sol --print→ completed:SOL61-OK."model":"gpt-6.1-sol", usageinput:5031, output:10, cost{"input":0.010062,"output":0.0001,"total":0.010162}— exactly 5031 × $2/M + 10 × $10/M, confirming the new catalog pricing end to end.openaiprovider.Suites:
pnpm run test:unit→ 3914/3922 pass; the 8 failures (gateway/MCP/orchestration env-dependent tests) fail identically on a pristinerelease/v0.121.6checkout with pi 0.87.1, so they are pre-existing and unrelated.pnpm run typecheckclean.oss/tests/pytest/unit/agents→ 1896 passed (includes the model-catalog coverage lock and capability guards).git diff --checkclean; noGitButler-Conflicttrailers.Review notes