Beast of Reincarnation: Cannot Talk to Kagura — Two Different Bugs
On PC it is almost certainly your interact keybind, and two players fixed it that way. On PS5 after the Chapter 2 boss it is a different fault with no fix — she repeats one line and sleeping is refused. Telling them apart first.
There are two of these and they are not related. On PC, an interact key that is bound to something else stops the dialogue starting at all — two players fixed it by rebinding, and v1.0.7 added a supported remap for that button. On PS5, after the Chapter 2 boss returns you to the Cleanse Walker, Kagura can repeat one line while the game refuses to let you sleep until you talk to her; that one reproduces on fresh saves and nobody has published a fix.
Where this is being asked · In r/BeastofReincarnation, where the PC case was posted as "Cant talk to kagura" by a player who assumed it was unique to him — "never heard anyone talks about this bug, is it only me?" — and the PlayStation case appeared underneath it from a different player who had lost nine hours to it.
A grade describes sourcing, not truth. Inferred means we concluded it and the reasoning is shown; unverified means someone asserted it and nobody stands behind it.
CorroboratedOn PC, rebinding the interact key restores the ability to talk to her.
Two players in one thread, independently: the asker who found it and a second who reported the same fix working.
Officialv1.0.7 added a setting to remap the interact button.
The official Steam patch notes, 9 August 2026. The notes do not connect it to this bug.
UnverifiedOn PS5 after the Chapter 2 boss, Kagura can repeat one line and block sleeping, reproducibly.
One player, who reproduced it from a fresh save in about two hours. Nobody has confirmed or contradicted it.
UnverifiedDefeating the Chapter 2 boss before the "talk to Kagura" objective appears avoids it.
The same player, describing which of his own saves worked. Not a tested procedure and not a recovery.
UnverifiedWhich default binding the PC conflict involves.
Nobody has said. The reporting player names a key he had set himself in a different game.
§01
Tell them apart before you try anything
The two faults share a sentence and nothing else, and the wrong branch costs real time in both directions: a PS5 player rebinding keys is fixing something that is not broken, and a PC player reading the softlock section is told a nine-hour save is dead when it is one setting away from working. Pick the symptom that matches what you are actually seeing.
Which one is yours?
§02
The PC case, and why the fix is easy to miss
The player who reported it worked it out himself and posted the answer: he changed the interact button off "f" and it worked immediately. He names the cause as a binding he had set in another game, where the same key was jump. A second player in the same thread reported the same fix working — "changed the talking keybind and it worked" — which is what moves this from a suggestion to a confirmed fix. What makes it easy to miss is that nothing on screen says the input is the problem: the dialogue simply does not start, which reads as a broken NPC rather than a broken binding.
Two independent confirmations, both in the same thread, neither contradicted.
v1.0.7 shipped "players can now remap the interact button in settings" — so on the current build this is a supported option rather than a workaround.
Nobody has said which default bindings conflict, so the fix is "change it", not "change it to X".
§03
The PlayStation case, which is a different animal
One player describes being returned to the Cleanse Walker automatically after the Chapter 2 boss, with Kagura repeating the line she used earlier in the chapter and the game refusing to let him sleep or move on until he speaks to her. He deleted the patch and reinstalled it, loaded every save he had, and then replayed to the same point on a fresh run in about two hours — and hit it again. That last detail is what makes it a progression bug rather than a corrupt save: it reproduced from a clean start.
The only thing he reports working is ordering: on the save where the Chapter 2 boss died *before* the objective to speak to Kagura appeared, sleeping and entering Chapter 3 both worked.
That is one player describing his own saves, not a tested procedure, and it recovers nothing for a save already stuck.
A Spanish-language report of a gate that will not reopen in the crater zone, and an English one of a subcity door that stays shut after the crank is turned, are being posted in the same week. Whether any of them share a cause is unknown and none is claimed here.
§04
What this page is not claiming
That these are the only two. That they share a cause — they almost certainly do not, since one is an input binding and the other survives a reinstall. That the PlayStation workaround will work for you, because it is one account of one player's save files and no second player has confirmed it. And nothing here is first-party: the developer has not acknowledged either fault, neither appears in the v1.0.7 notes as a fix, and the publisher's own feedback form is where a reproducible progression blocker should go.
Expiry condition
What would have to change for this answer to be wrong
An answer about a live-service game without this is an answer with a hidden expiry date.
A patch note names either fault, which would move it to the tracker. Or a second PlayStation player confirms the ordering workaround, which would raise it from one account to a procedure. Or somebody establishes which default binding the PC conflict actually involves, which would turn "change your interact key" into a specific instruction.
Citations
Every source, with its date
A complaint posted before 30 July 2026 describes the playtest, not the game you bought, and a source whose publication date nobody captured cannot show that it postdates launch either. Both are flagged rather than quietly mixed in.
Both faults, in one thread. The asker reports the PC symptom and later posts his own fix — rebinding the interact key off "f" — and a second player confirms the same fix worked. Separately, a PlayStation player reports the Cleanse Walker softlock after the Chapter 2 boss, its reproduction on a fresh two-hour run, and that reinstalling the patch did not help.
The same PlayStation player's longer account, including the ordering workaround: that on a save where the Chapter 2 boss was defeated before the objective to talk to Kagura appeared, sleeping and progressing worked. One player, his own saves, no second confirmation.
That v1.0.7 added the ability to remap the interact button in settings. It does not mention Kagura, either fault, or dialogue failing to start — the connection to the PC case is ours, and it is that the patch makes the players' fix a supported option rather than that the patch was a response to it.
Related questions
On PC it is most likely your interact keybind — two players fixed it by rebinding that button, and v1.0.7 added a setting for it. On PS5 after the Chapter 2 boss there is a separate fault where she repeats one line and sleeping is refused, and that one has no published fix.
