feat: add Stability AI image edit models support to Bedrock provider

[Radheshg04]

Summary

Adds support for Stability AI image editing models in the Bedrock provider, expanding image editing capabilities beyond the existing Titan and Nova Canvas models.

Changes

• Added getStabilityAIEditTaskType() function to infer edit task types from Stability AI model names (inpaint, outpaint, recolor, search-replace, erase-object, remove-bg, control-sketch, control-structure, style-guide, style-transfer, upscale-creative, upscale-conservative, upscale-fast)
• Created ToStabilityAIImageEditRequest() function to convert Bifrost requests to Stability AI's flat JSON format, with task-specific field validation
• Added StabilityAIImageEditRequest struct with comprehensive field support for all Stability AI edit operations
• Enhanced BedrockImageGenerationResponse with Seeds and FinishReasons fields for Stability AI compatibility
• Modified ImageEdit() method to route requests to appropriate conversion function based on model type
• Updated documentation to reflect expanded model support

Type of change

• Feature
• Bug fix
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (Next.js)
• Docs

How to test

Test with various Stability AI edit models through the Bedrock provider:

# Core/Transports
go version
go test ./...

# Test image editing with Stability AI models
# Example: stable-image-inpaint, stable-outpaint, stable-creative-upscale, etc.

Verify that task-specific parameters are correctly mapped and invalid fields are filtered out based on the detected task type.

Screenshots/Recordings

N/A - Backend functionality only

Breaking changes

• Yes
• No

Related issues

N/A

Security considerations

Image data is handled as base64-encoded strings. Mask and image parameters are properly validated before processing.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5007b7e4-d414-4753-a0d8-61bc20604f81

📥 Commits

Reviewing files that changed from the base of the PR and between 1c6080c and 13f5d89.

📒 Files selected for processing (8)

• core/bifrost.go
• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go
• core/schemas/images.go
• core/utils.go
• docs/providers/supported-providers/bedrock.mdx
• transports/bifrost-http/handlers/inference.go

---

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• New Features

  • Added support for Stability AI image editing models in Bedrock provider
  • Expanded image edit capabilities with multiple task types including inpaint, style transfer, outpaint, remove background, erase object, recolor, search-replace, and upscale variations
  • Improved prompt handling—prompt is now optional for certain image edit task types

• Documentation

  • Updated Bedrock provider documentation with Stability AI image generation and editing specifications, supported model IDs, and request examples

Walkthrough

Bedrock ImageEdit now detects Stability AI deployments, resolves model path/deployment once, and routes Stability edits through a new Stability-specific converter and request type; non‑Stability models continue using the existing Bedrock converter and flow.

Changes

Cohort / File(s)	Summary
Provider routing core/providers/bedrock/bedrock.go	Resolve model path/deployment once up front; choose ToStabilityAIImageEditRequest when deployment indicates Stability, otherwise ToBedrockImageEditRequest; reuse resolved values for request execution and response metadata.
Stability edit conversion core/providers/bedrock/images.go	Add task/type mapping and inference (getStabilityAITaskTypeFromParams, getStabilityAIEditTaskType) and ToStabilityAIImageEditRequest to validate input, infer/require task, map images/mask/seed/prompts, extract/normalize typed extra_params, and build flat Stability-style edit payloads.
Types & responses core/providers/bedrock/types.go	Add StabilityAIImageEditRequest type with task-scoped optional fields and GetExtraParams(); extend BedrockImageGenerationResponse to include Seeds []int and FinishReasons []*string.
Validation & helpers core/bifrost.go, core/utils.go, transports/bifrost-http/handlers/inference.go	Introduce isPromptOptionalImageEditType and relax prompt-required validation for additional edit types; remove strict multipart prompt enforcement in HTTP handler.
Schema docs core/schemas/images.go	Expand inline ImageEditParameters.Type comment to list additional edit modes (e.g., remove_background, erase_object, recolor, search_replace, style_transfer, upscale_*).
Documentation docs/providers/supported-providers/bedrock.mdx	Document Stability AI model support for Image Generation/Edit, flat JSON format for Stability, automatic model detection, task inference rules, supported models/tasks, parameter tables, and example flows.

Sequence Diagram(s)

sequenceDiagram
  participant Client as Client
  participant Provider as BedrockProvider
  participant Converter as StabilityConverter
  participant API as BedrockAPI

  Client->>Provider: ImageEdit(request: model, images, params)
  Provider->>Provider: getModelPath("invoke", model) -> path/deployment
  alt deployment contains "stability."
    Provider->>Converter: ToStabilityAIImageEditRequest(request, deployment)
    Converter-->>Provider: StabilityAIImageEditRequest
    Provider->>API: Invoke (Stability flat JSON / multipart)
  else non-Stability model
    Provider->>Provider: ToBedrockImageEditRequest(request)
    Provider->>API: Invoke (Bedrock JSON)
  end
  API-->>Provider: Response (images, seeds?, finish reasons?)
  Provider-->>Client: Normalized BedrockImageGenerationResponse

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• feat: add Stability AI image edit models support to Bedrock provider #2225 — Adds Stability AI image-edit support and the same Bedrock provider changes (Stability converters and types), modifying overlapping functions and types.

Poem

🐰 I hopped through code with a curious twitch,

Found "stability." stamped—so I made the switch,
I nibble prompts, masks, and two-image tricks,
I sort extra params and stitch,
Edits ready—hop, click, fix! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 71.43% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add Stability AI image edit models support to Bedrock provider' directly and specifically describes the main feature addition—Stability AI support for image editing in the Bedrock provider.
Description check	✅ Passed	The PR description covers all major template sections: summary, changes, type of change, affected areas, how to test, breaking changes, security considerations, and a completed checklist.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 03-23-feat_adds_stabilityai_image_edit_support

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Radheshg04]

• feat: add Stability AI image edit models support to Bedrock provider #2225 👈 (View in Graphite)
• feat: add Stability AI model support for Bedrock image generation #2180 : 1 other dependent PR (#2181 )
• feat(pricing): implement scoped pricing overrides #1825 : 1 other dependent PR (#2178 )
• v1.5.0

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/providers/bedrock/bedrock.go`:
- Around line 1944-1949: The ImageEdit converter closure currently decides
between ToStabilityAIImageEditRequest and ToBedrockImageEditRequest by calling
isStabilityAIModel(request.Model); change it to use the already-resolved
deployment identifier (the same deployment used by ImageGeneration at Line 1956)
instead of request.Model, and ensure any subsequent Stability-specific logic
(e.g., getStabilityAIEditTaskType) also derives its task/type from that resolved
deployment value rather than the raw request model; update references to
isStabilityAIModel and task inference to use deployment so mappings like
key.BedrockKeyConfig.Deployments -> "stability.*" route correctly.

In `@core/providers/bedrock/images.go`:
- Around line 459-466: The style-transfer branch currently only checks for two
image entries but doesn't validate their payloads; before base64 encoding in the
block that sets req.InitImage and req.StyleImage, verify that
request.Input.Images[0].Image and request.Input.Images[1].Image are non-empty
and return an error (similar to the non-style-transfer path) if either is empty
so you don't emit empty init_image/style_image fields; update the logic around
the style-transfer conditional that encodes images to perform these nil/length
checks and return a descriptive fmt.Errorf when validation fails.
- Around line 511-621: The converter currently mutates the caller-owned
request.Params.ExtraParams via ep := request.Params.ExtraParams and delete(...)
calls; make it pure by cloning ExtraParams into a new map (e.g., cloned :=
make(map[string]any); for k,v := range request.Params.ExtraParams { cloned[k]=v
}) and then use cloned in place of ep for all SafeExtract... and delete(...)
operations, finally set req.ExtraParams = cloned so the original
request.Params.ExtraParams is not modified (update references to ep
accordingly).

In `@core/providers/bedrock/types.go`:
- Around line 822-829: The BedrockImageGenerationResponse struct currently
includes dead fields Seeds and FinishReasons that are parsed but never
propagated because BedrockProvider.ImageGeneration / ImageEdit use
ToBifrostImageGenerationResponse, which only copies Images; either remove these
unused fields from BedrockImageGenerationResponse to avoid misleading
compatibility, or update the conversion path—specifically
ToBifrostImageGenerationResponse and any related Bifrost image response types—to
copy Seeds and FinishReasons through so they reach the Bifrost response; locate
the symbols BedrockImageGenerationResponse, Seeds, FinishReasons,
ToBifrostImageGenerationResponse, BedrockProvider.ImageGeneration and ImageEdit
and apply the chosen change consistently across those functions/types.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0d47349b-552d-40c3-8f48-dad14404b58c

📥 Commits

Reviewing files that changed from the base of the PR and between 0d15eae and c7f5a15.

📒 Files selected for processing (3)

• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/providers/bedrock/images.go`:
- Around line 516-526: The converter currently only reads "output_format" from
request.Params.ExtraParams (ep) and therefore ignores a typed
params.output_format; update the mapping to first check
request.Params.OutputFormat (the typed field on ImageEditParameters) and, if
set, assign it to req.OutputFormat, otherwise fall back to extracting
"output_format" from ep using schemas.SafeExtractStringPointer. Make the same
change for the similar block around the other occurrence (the lines referenced
near 629-630), ensuring you reference request.Params,
request.Params.OutputFormat, ep, schemas.SafeExtractStringPointer, and
req.OutputFormat so typed params take precedence over ExtraParams.
- Around line 439-441: The error returned in the default branch uses "Stability
AI" with capital letters; update the fmt.Errorf call to use lowercase wording
and follow Go error-string convention (e.g., "cannot determine task type from
stability ai model name %q") while keeping the %q model interpolation and no
trailing punctuation; locate the fmt.Errorf(...) that returns the error in the
default case (uses fmt.Errorf and the model variable) in
core/providers/bedrock/images.go and replace the message accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b7dc07b4-235c-48b1-bde5-70935bd4f182

📥 Commits

Reviewing files that changed from the base of the PR and between c7f5a15 and 425b81c.

📒 Files selected for processing (4)

• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go
• docs/providers/supported-providers/bedrock.mdx

👮 Files not reviewed due to content moderation or server errors (3)

• core/providers/bedrock/types.go
• core/providers/bedrock/bedrock.go
• docs/providers/supported-providers/bedrock.mdx

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/providers/bedrock/bedrock.go`:
- Around line 1948-1953: The current branch that builds the request/response
conversion picks ToStabilityAIImageEditRequest for Stability models but then
later feeds the resulting BedrockImageGenerationResponse directly into
ToBifrostImageGenerationResponse which only copies Images, dropping the new
Seeds and FinishReasons metadata; update the conversion flow so that after
calling ToStabilityAIImageEditRequest (and the analogous StabilityAI
generation/edit paths at the other location), you extract and surface Seeds and
FinishReasons from the BedrockImageGenerationResponse and propagate them into
the Bifrost response (i.e., enhance or extend ToBifrostImageGenerationResponse
or add a wrapper step) so that Seeds and FinishReasons from
BedrockImageGenerationResponse are preserved rather than discarded. Ensure
changes reference ToStabilityAIImageEditRequest, ToBedrockImageEditRequest,
BedrockImageGenerationResponse, and ToBifrostImageGenerationResponse so
reviewers can find and update the correct conversion logic.

In `@core/providers/bedrock/images.go`:
- Around line 480-503: Update the taskType allowlists in
core/providers/bedrock/images.go so they match the Bedrock/Stability contract:
include "erase-object" in the switch cases that set req.Prompt and
req.NegativePrompt (so erase-object retains prompt and negative_prompt), and
include "upscale-fast" in the switch case that assigns req.Seed (so upscale-fast
preserves seed); locate the blocks where req.Prompt, req.NegativePrompt, and
req.Seed are populated and adjust the case lists to exactly mirror the new
Stability docs.
- Around line 461-466: The style-transfer branch currently allows >=2 images and
silently ignores extras; change the validation to require exactly two images by
checking that len(request.Input.Images) == 2 (use taskType and
request.Input.Images to locate the block), and return a clear error when the
length is not exactly 2 (update the error text to state "style-transfer requires
exactly two images: init_image and style_image" and keep the non-empty checks
for both request.Input.Images[0].Image and request.Input.Images[1].Image).
Ensure no further code assumes a variable number of images beyond these two.

In `@docs/providers/supported-providers/bedrock.mdx`:
- Around line 910-936: The tables are inconsistent about mask: the model matrix
marks `inpaint` and `erase-object` as "1 + mask" but the Common parameters list
`mask` as optional; update the Common parameters to make `mask` required for
those tasks by changing the `mask` row to Required: ✅ and set Notes to "Required
for: `inpaint`, `erase-object`; optional/ignored for others" (or alternatively
remove the "+ mask" from the model matrix if you prefer masks to be
optional—pick one contract and apply it consistently); ensure references to
`inpaint`, `erase-object`, and the `mask` parameter reflect the chosen contract.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bf9b437d-e5d8-4e30-854c-8570432464f1

📥 Commits

Reviewing files that changed from the base of the PR and between 425b81c and 8719cb6.

📒 Files selected for processing (4)

• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go
• docs/providers/supported-providers/bedrock.mdx

🚧 Files skipped from review as they are similar to previous changes (1)

• core/providers/bedrock/types.go

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/providers/supported-providers/bedrock.mdx`:
- Around line 910-924: Update the model table row for
`stability.stable-image-erase-object-v1:0` in
docs/providers/supported-providers/bedrock.mdx so the Prompt column reflects
that prompts are not required (change the ✅ to ❌) to match the text and the
images.go logic; verify the entry for `stability.stable-image-erase-object-v1:0`
is the one you change and cross-check images.go’s prompt allowlist that excludes
"erase-object" to ensure consistency.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f5d12690-903f-4c25-92cc-fc925cf74541

📥 Commits

Reviewing files that changed from the base of the PR and between 8719cb6 and 650fc3c.

📒 Files selected for processing (4)

• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go
• docs/providers/supported-providers/bedrock.mdx

🚧 Files skipped from review as they are similar to previous changes (2)

• core/providers/bedrock/types.go
• core/providers/bedrock/bedrock.go

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/bifrost.go`:
- Around line 1251-1257: The prompt validation fails for hyphenated edit types
because imageEditType (set from req.Params.Type) is only lowercased but not
normalized; update the logic that computes imageEditType used in the
slices.Contains check (and any related checks) to normalize hyphens to
underscores (or otherwise canonicalize variants like "erase-object" ->
"erase_object", "remove-bg" -> "remove_background", "upscale-fast" ->
"upscale_fast") before checking the allowlist, so that the existing allowlist of
underscore forms matches hyphenated inputs; keep the isLargePayloadPassthrough
check and existing slices.Contains call unchanged except for using the
normalized imageEditType.

In `@core/providers/bedrock/images.go`:
- Around line 557-679: The ExtraParams handling must validate required per-task
fields and remove extras incompatible with the chosen task: after populating
req.* fields and before assigning req.ExtraParams = ep, add per-task validation
(if taskType == "recolor" ensure req.SelectPrompt is non-empty and return an
error if missing; if taskType == "search-replace" ensure req.SearchPrompt is
non-empty and return an error if missing; if taskType == "outpaint" ensure at
least one of req.Left, req.Right, req.Up, req.Down is non-zero and return an
error if not). Also filter ep to remove any keys not allowed for the current
task (define an allowed-key set per taskType and delete any ep entries outside
that set) so req.ExtraParams only contains permissible extras; use the existing
symbols taskType, req.SelectPrompt, req.SearchPrompt, req.Left/Right/Up/Down,
and req.ExtraParams to locate where to add these checks and the filtering logic.
- Around line 488-498: Currently the code trusts request.Params.Type before
validating against the resolved deployment, allowing a mismatch; instead, call
getStabilityAIEditTaskType(deployment) first to determine the canonical taskType
for the resolved model, then if request.Params != nil && request.Params.Type !=
nil call getStabilityAITaskTypeFromParams and compare the explicit type to the
canonical one and return an error if they differ or if the explicit value is
unknown; preserve existing error handling from getStabilityAIEditTaskType and
use a clear error when the explicit type mismatches the deployment.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e7285bb2-c967-4912-892b-4e1f409b7584

📥 Commits

Reviewing files that changed from the base of the PR and between bded024 and 75b33e7.

📒 Files selected for processing (7)

• core/bifrost.go
• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go
• core/schemas/images.go
• docs/providers/supported-providers/bedrock.mdx
• transports/bifrost-http/handlers/inference.go

💤 Files with no reviewable changes (1)

• transports/bifrost-http/handlers/inference.go

✅ Files skipped from review due to trivial changes (2)

• core/schemas/images.go
• docs/providers/supported-providers/bedrock.mdx

🚧 Files skipped from review as they are similar to previous changes (1)

• core/providers/bedrock/bedrock.go

[coderabbitai]

Actionable comments posted: 1

♻️ Duplicate comments (2)

docs/providers/supported-providers/bedrock.mdx (1)

910-917: ⚠️ Potential issue | 🟡 Minor

The Stability edit tables still overstate mask requirements and miss the outpaint constraint.

Bedrock treats mask as optional for inpaint and erase-object because it can derive the mask from the input image’s alpha channel, and it requires outpaint to include at least one non-zero left/right/up/down value. The current model matrix/common-parameter rows still say mask is required for inpaint/erase-object, and the outpaint row never mentions the non-zero-direction requirement. (docs.aws.amazon.com)

📝 Suggested doc update

-| `stability.stable-image-inpaint-v1:0` | inpaint | 1 + mask | ✅ |
+| `stability.stable-image-inpaint-v1:0` | inpaint | 1 (mask optional) | ✅ |
...
-| `stability.stable-image-erase-object-v1:0` | erase-object | 1 + mask | ❌ |
+| `stability.stable-image-erase-object-v1:0` | erase-object | 1 (mask optional) | ❌ |
...
-| `mask` | binary | task-dependent | Required for: `inpaint`, `erase-object`; ignored for others |
+| `mask` | binary | ❌ | Optional for: `inpaint`, `erase-object` (Bedrock derives it from the image alpha channel if omitted); ignored for others |
...
-| `left`, `right`, `up`, `down` | int | outpaint — pixels to expand in each direction |
+| `left`, `right`, `up`, `down` | int | outpaint — pixels to expand in each direction; at least one non-zero value is required |

Also applies to: 928-946

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/providers/supported-providers/bedrock.mdx` around lines 910 - 917, The
Stability model table rows misstate mask and outpaint requirements: update the
rows for `stability.stable-image-inpaint-v1:0` and
`stability.stable-image-erase-object-v1:0` to mark `mask` as optional (not
required) because Bedrock can derive masks from image alpha, and update the
`stability.stable-outpaint-v1:0` row to note that outpaint requires at least one
non-zero direction value (`left`/`right`/`up`/`down`); adjust any related
model-matrix or common-parameter notes accordingly so `inpaint`/`erase-object`
show optional mask and `outpaint` explicitly documents the non-zero-direction
constraint.

core/providers/bedrock/images.go (1)

597-615: ⚠️ Potential issue | 🟠 Major

Reject outpaint requests with no expansion direction.

This path still returns an outpaint body even when left, right, up, and down are all unset or zero. Bedrock requires at least one of those directions to be supplied with a non-zero value, so this should fail fast instead of sending an invalid request downstream. (docs.aws.amazon.com)

💡 Suggested fix

 			// outpaint directional fields
 			if taskType == "outpaint" {
 				if v, ok := schemas.SafeExtractIntPointer(ep["left"]); ok {
 					delete(ep, "left")
 					req.Left = v
 				}
 				if v, ok := schemas.SafeExtractIntPointer(ep["right"]); ok {
 					delete(ep, "right")
 					req.Right = v
 				}
 				if v, ok := schemas.SafeExtractIntPointer(ep["up"]); ok {
 					delete(ep, "up")
 					req.Up = v
 				}
 				if v, ok := schemas.SafeExtractIntPointer(ep["down"]); ok {
 					delete(ep, "down")
 					req.Down = v
 				}
+
+				hasDirection := (req.Left != nil && *req.Left != 0) ||
+					(req.Right != nil && *req.Right != 0) ||
+					(req.Up != nil && *req.Up != 0) ||
+					(req.Down != nil && *req.Down != 0)
+				if !hasDirection {
+					return nil, fmt.Errorf("outpaint requires at least one non-zero direction")
+				}
 			}

Also applies to: 683-691

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@core/providers/bedrock/images.go` around lines 597 - 615, When handling
taskType == "outpaint" in core/providers/bedrock/images.go (the block that
extracts left/right/up/down using schemas.SafeExtractIntPointer into
req.Left/Right/Up/Down), validate after extraction that at least one of
req.Left, req.Right, req.Up, req.Down is non-nil AND has a non-zero value; if
none are set, return an error / reject the request immediately instead of
constructing an outpaint body. Apply the same validation to the second outpaint
extraction block referenced around the 683-691 region.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/providers/bedrock/images.go`:
- Around line 410-439: The getStabilityAITaskTypeFromParams function is missing
the documented alias "remove_bg", causing explicit remove_bg types to be
ignored; update the switch in getStabilityAITaskTypeFromParams to include a case
for "remove_bg" that returns "remove-bg" (alongside the existing
"background_removal" / "remove_background" cases) so
ToStabilityAIImageEditRequest will honor explicit remove_bg task types for
aliased/custom deployments.

---

Duplicate comments:
In `@core/providers/bedrock/images.go`:
- Around line 597-615: When handling taskType == "outpaint" in
core/providers/bedrock/images.go (the block that extracts left/right/up/down
using schemas.SafeExtractIntPointer into req.Left/Right/Up/Down), validate after
extraction that at least one of req.Left, req.Right, req.Up, req.Down is non-nil
AND has a non-zero value; if none are set, return an error / reject the request
immediately instead of constructing an outpaint body. Apply the same validation
to the second outpaint extraction block referenced around the 683-691 region.

In `@docs/providers/supported-providers/bedrock.mdx`:
- Around line 910-917: The Stability model table rows misstate mask and outpaint
requirements: update the rows for `stability.stable-image-inpaint-v1:0` and
`stability.stable-image-erase-object-v1:0` to mark `mask` as optional (not
required) because Bedrock can derive masks from image alpha, and update the
`stability.stable-outpaint-v1:0` row to note that outpaint requires at least one
non-zero direction value (`left`/`right`/`up`/`down`); adjust any related
model-matrix or common-parameter notes accordingly so `inpaint`/`erase-object`
show optional mask and `outpaint` explicitly documents the non-zero-direction
constraint.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dad41025-2de9-428f-8d8f-01c2c2534dae

📥 Commits

Reviewing files that changed from the base of the PR and between 75b33e7 and 1c6080c.

📒 Files selected for processing (7)

• core/bifrost.go
• core/providers/bedrock/bedrock.go
• core/providers/bedrock/images.go
• core/providers/bedrock/types.go
• core/schemas/images.go
• docs/providers/supported-providers/bedrock.mdx
• transports/bifrost-http/handlers/inference.go

💤 Files with no reviewable changes (1)

• transports/bifrost-http/handlers/inference.go

✅ Files skipped from review due to trivial changes (1)

• core/schemas/images.go

🚧 Files skipped from review as they are similar to previous changes (3)

• core/providers/bedrock/bedrock.go
• core/bifrost.go
• core/providers/bedrock/types.go

[Pratham-Mishra04]

Merge activity

• Mar 23, 1:53 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 23, 1:56 PM UTC: Graphite rebased this pull request as part of a merge.
• Mar 23, 1:57 PM UTC: @Pratham-Mishra04 merged this pull request with Graphite.