[bug]: Newly generated images go into previous board instead of newly-created one

[shanedk]

Is there an existing issue for this problem?

• I have searched the existing issues

Install method

Invoke's Launcher

Operating system

Windows

GPU vendor

Nvidia (CUDA)

GPU model

RTX 3060

GPU VRAM

12GB

Version number

6.13.0rc2

Browser

No response

System Information

Starting with 6.13rc2 (I don't know whether or not the problem existed in rc1), when you create a new board and generate images, they get put into the previously-selected board instead of the new one.

What happened

• Be in a Board in the Generate tab
• Create a new Board
• Select the new Board
• Generate images
• Notice they go into the previously-selected board

What you expected to happen

They should have gone into the new board.

How to reproduce the problem

1. Select a board
2. Create a new board
3. Select the new board
4. Generate some images

Additional context

No response

Discord username

shanedk

[Pfannkuchensack]

I can't reproduce this. If I create a board and then click on it immediately afterwards, it's selected and images are saved to it.
There is a Option that changes that behaviors.

[shanedk]

That option is checked for me. The issue is, when the new board is created, it's selected and there's no clue you have to click on the board to save the images there.

2026-05-15.08-01-16.mp4

[JPPhoto]

This looks like a potential UX inconsistency, but the question is if this is really an issue to fix.

Currently, board creation only updates gallery selection:

invokeai/frontend/web/src/features/gallery/components/Boards/BoardsList/AddBoardButton.tsx:16 creates the board, then dispatches boardIdSelected(...), but does not update autoAddBoardId.

Clicking an existing board does update both when "Auto-Assign Board on Click" is enabled:

invokeai/frontend/web/src/features/gallery/components/Boards/BoardsList/GalleryBoard.tsx:42 dispatches boardIdSelected(...), then conditionally dispatches autoAddBoardIdChanged(...).

Generated outputs use autoAddBoardId, not selectedBoardId:

invokeai/frontend/web/src/features/nodes/util/graph/graphBuilderUtils.ts:32 and invokeai/frontend/web/src/features/nodes/util/graph/buildNodesGraph.ts:21 route board fields through the auto-add board. The invoke tooltip also reports the destination from autoAddBoardId in invokeai/frontend/web/src/features/queue/components/InvokeButtonTooltip/InvokeButtonTooltip.tsx:251.

Therefore, the reported behavior makes sense:

1. User is on Board A, so auto-add is Board A.
2. User creates Board B.
3. UI selects Board B, but auto-add remains Board A.
4. Generation saves to Board A.
5. Clicking Board B fixes it because the board click handler updates auto-add.

If we choose to fix this, the likely path is to have AddBoardButton also dispatch autoAddBoardIdChanged(board.board_id) when autoAssignBoardOnClick is enabled, or otherwise make newly-created board selection use the same "select and auto-assign" path as a real board click.

@Pfannkuchensack @joshistoast Thoughts?

[joshistoast]

@JPPhoto I've experienced this UX inconsistency first-hand and, while I deal with it, would prefer the board auto assign to just know what board I'm on. So we'd probably also rename all the "on click" verbiage to just "auto assign board".

[Pfannkuchensack]

That option is checked for me. The issue is, when the new board is created, it's selected and there's no clue you have to click on the board to save the images there.

2026-05-15.08-01-16.mp4

ah yes, i did click on it after the create of the board.