Kewa is not a passive mount. The giant space whale carrying your Peeps has their own mood, their own dialogue, and their own travel agenda, and every Beyond These Stars Kewa request is a soft warning that the planet under your feet is about to change. Dev Blog #29 is explicit: a hot galaxy drags Kewa's happiness down, and if it falls far enough, Kewa starts emergency travel somewhere cold. That single sentence is the reason this system exists, and it is also the reason a player who ignores the dialogue box often wakes up to a missing settlement. For the primary source, see the Kewa happiness dev blog.
This guide walks through the verified request loop: what triggers a request, how temperature and biome health feed into it, what the developer has and has not published about the outcome, and how to read the warning signs before Kewa leaves the system. Everything below is sourced from the official store page, the developer's dev blog archive, and the launch-day presskit — the only materials that exist one day after release.
What "Kewa Requests" Actually Means in Beyond These Stars
Kewa speaks. The game opens with your first conversation, and from that point the whale surfaces requests in a dialogue layer on top of the city-building layer underneath. A Beyond These Stars Kewa request is any dialogue prompt that asks the player to change something on or around the living platform — a biome adjustment, a course correction, a mood repair, or an emergency relocation. The request system is the in-fiction reason the galaxy map matters: Kewa is not just carrying you, Kewa is choosing where to go, and they will tell you when the current route stops working.
The core entities that interact with this loop are the Peeps (your colonists), Kewa (the sentient space whale), and the wider Galaxy Map that Kewa moves across. The loop ties three official systems together: the dialogue choice system (Dev Blog series on Kewa wants), the Temperature system (Dev Blog #29 on hot vs. cold galaxies), and the Biome Health system (also Dev Blog #29: planting trees, minimising pollution, and creating rivers keep the biome healthy). Every request Kewa raises touches at least one of those three.
| Request category | What Kewa is reacting to | Primary system | What the player is asked to do |
|---|---|---|---|
| Biome temperature complaint | A hot galaxy pushing Kewa's happiness down | Temperature / Galaxy Map | Cool the biome, plant trees, or change course |
| Pollution complaint | Toxic tiles, smokestack output, and missing Tree Nursery cover | Biome Health | Build a Cleaner, add Tree Nurseries, dig a river |
| Emergency travel warning | A threshold Kewa will not stay below | Dialogue → Galaxy Map | Agree to relocation, or refuse and lose them |
| Resource stress request | A planet or outpost not producing what Kewa needs | Production chains (Kewa-adjacent) | Open a Space Port route, settle a new planet |
| Settlement / outpost request | A nearby planet is settleable, and Kewa wants the colony to spread | Outpost layer | Send a Settlement Ship (not player-built) |
The dialogue is the only UI element that surfaces the request — there is no quest log entry, no pop-up banner. If you skip past the dialogue, you skip past the request, and the only signal that you missed it will be a sudden course change on the galaxy map or a happiness drop in the Kewa panel. The developer has not published a notification system or a request log, so reading the dialogue as it appears is the only verified way to catch a request in time.
Why requests are not the same as achievements
A common first-week confusion is to treat Kewa's dialogue as a checklist. It is not. Requests are state-driven: they appear when a variable crosses a threshold the developer has described at type level (a happiness threshold, a temperature threshold, a biome-health threshold), and they disappear once that variable is corrected. The 64 achievements in the base game may track some of these thresholds, but the developer has not published which achievements bind to which request. As of the October 2026 launch, the link between specific request outcomes and specific achievement unlocks is not in the official material.
Kewa Temperature, Hot Galaxies, and the Verified Threshold Behaviour
Dev Blog #29 is the only official source that ties temperature to Kewa's mood, and it is short. The relevant facts are: a hot galaxy drags Kewa's happiness down, and if happiness falls far enough, Kewa starts emergency travel somewhere cold. The developer has not published the exact happiness number that triggers emergency travel, the exact temperature value that counts as "hot", or the in-game day on which the request first surfaces. What is published is the direction of the relationship and the existence of the threshold.
The verified chain reads: hot galaxy → Kewa happiness falls → dialogue request appears → if player ignores, Kewa begins emergency travel → colony relocates to a colder system. The chain is causal, not optional. The developer has confirmed the chain by writing it directly into Dev Blog #29; the developer has not confirmed any numbers inside it.
| Variable | Developer-confirmed direction | Developer-published value | What the player observes |
|---|---|---|---|
| Galaxy temperature (hot) | Lowers Kewa happiness | Not published | Kewa panel drops; dialogue fires |
| Galaxy temperature (cold) | Raises Kewa happiness | Not published | Kewa panel rises; dialogue calms |
| Kewa happiness threshold (emergency travel) | Triggers relocation if crossed | Not published | Galaxy map shows a new course |
| Biome health (planted trees, low pollution, rivers) | Holds the biome healthy | Not published | Toxic tiles shrink; atmosphere spreads |
| Pollution output | Damages biome health if not addressed | Not published | Cleaners become more important; trees become slower to plant |
The two-sided nature of the system is what makes it manageable. A hot galaxy is a pressure, but a cold galaxy is a relief. A player who notices the temperature reading on the galaxy map can plan a route that mostly hugs cold or moderate stars and only briefly enters hot regions for resources they cannot find elsewhere. The verified Neutral Sector — named in Dev Blog #28 — is a moderate-climate region with a planet that holds chickens and cows, and it is the canonical example of a "neutral" temperature a player can settle without triggering a temperature complaint from Kewa.
The "emergency travel" wording is not a bluff
A few launch-day players (based on community reports from the Steam discussion thread, current as of October 17 2026) have suggested that ignoring the temperature warning only delays the dialogue. Dev Blog #29 contradicts that read. The wording is "Kewa starts emergency travel", and the only published outcome of that travel is that the colony ends up somewhere cold. The developer has not described a soft version of this event where the player can simply refuse and stay in the hot system, and they have not published a cooldown after which Kewa asks again. Until that is published, treat the request as binding: when Kewa asks to move, the move is on the table.
Reading the Dialogue Before Kewa Leaves the System
A Beyond These Stars Kewa request surfaces in a dialogue box, and the player has two to four choices depending on the request type. The dialogue system is the same layer described in the Kewa wants system guide: a request appears, the player picks a response, and Kewa's happiness nudges up or down based on whether the request was honoured. The launch trailer (official) shows the same flow at a higher pace, but the in-game cadence is slow and readable.
The two warning signs that a request is about to escalate are: (1) Kewa is repeating the same line more than once across several shifts, and (2) the Kewa happiness panel has dropped visibly without a matching Peep-side reason. If both signs are present, the next request is almost certainly a temperature-driven or biome-driven escalation, and the player should be ready to either correct the underlying system or agree to the relocation dialogue option.
| Warning sign | Likely request type | Best immediate response |
|---|---|---|
| Kewa repeats a biome complaint | Pollution / toxic tiles | Build a Cleaner, add Tree Nurseries, dig a river |
| Kewa mentions heat for the first time | Temperature | Check the galaxy map; plan a cold-route course |
| Kewa mentions cold for the first time after a hot stretch | Temperature relief | No action needed; ride the relief |
| Kewa asks about an empty nearby planet | Settlement / outpost request | Send the Settlement Ship to that node |
| Kewa asks to leave a hot system entirely | Emergency travel | Agree and pick the cold destination carefully |
The "pick the cold destination carefully" line is the one piece of practical advice the developer has implicitly endorsed by writing the galaxy map in Dev Blog #28. The galaxy map is partially visible at first and unlocks over time, and nodes hold barren planets, space junk, strange objects, trade stations, and aliens. A cold destination that is also barren and empty will solve the temperature problem and create a resource problem on the same shift, so a player who is forced into emergency travel should aim for a cold node that already shows a planet icon and at least one resource on the scan.
What "Beyond These Stars why did Kewa leave" actually answers
Players searching for that phrase after the fact are usually looking at an empty platform and an unfamiliar course on the galaxy map. The verified answer is the temperature chain above. The not-yet-verified answer — what the developer has not yet published — includes the exact threshold number, the exact course Kewa picks, and whether the original system is ever revisited. Until those are published, the practical answer to "why did Kewa leave" is "because the temperature pushed happiness past the emergency travel threshold, and the player did not address it in time."
What Happens If You Ignore the Request
The verified consequence of ignoring a temperature request is emergency travel. The verified consequence of ignoring a biome-health request is a longer happiness slide that compounds into the same emergency travel chain. The verified consequence of ignoring a resource request is a slower city, not a relocation. Everything past that is not in the official material.
A common worry is that ignoring a request will softlock the game, lock achievements, or end the run. The developer has not published any of those outcomes. Story Mode has a defined ending arc; Sandbox Mode is open-ended; achievements total 64 across the base game. None of the official channels describe a fail state triggered by ignoring Kewa, only a state change (the platform relocates, the player is in a colder system, and the new biome is a clean slate that the player has to re-terraform). The same loop described in the symbiotic relationship guide applies: Kewa and the colony are coupled, and the cost of being out of sync with Kewa is relocation, not game over.
| Action | Verified outcome | Not yet published |
|---|---|---|
| Address a temperature request | Kewa happiness recovers; galaxy course may bend | Exact recovery rate |
| Address a biome-health request | Toxic tiles shrink; trees spread atmosphere | Exact tile-per-shift rate |
| Ignore a temperature request | Kewa begins emergency travel somewhere cold | Exact threshold; exact destination logic |
| Ignore a biome-health request | Happiness slides; eventual temperature chain | Exact slide rate per shift |
| Ignore a resource request | Production slows; no relocation | Exact slow-down multiplier |
| Refuse emergency travel dialogue | Developer has not published this option | Whether refusal is allowed at all |
The "developer has not published this option" line is important. The dialogue tree may or may not include a refusal branch for emergency travel; the launch build does not have an official description of that branch. A player who wants to keep a hot system can experiment, but should not assume the option is there.
Building a Settlement That Pre-Empts the Worst Requests
A pre-emptive playstyle is the cleanest way to avoid the worst-case version of a Beyond These Stars Kewa request. The verified pre-emptive moves are all Dev Blog #29 moves: plant trees, minimise pollution, and create rivers. None of these is hidden; all three are described in the same post that describes the temperature chain. The order matters less than the coverage — a single Tree Nursery on a platform with twenty Cleaners will still leave toxic tiles, and a dense forest with no Cleaners will still lose ground to the smokestacks.
| Pre-emptive move | What it does | Cost in the early game | When to add it |
|---|---|---|---|
| Tree Nursery | Plants trees, which spread atmosphere and offset pollution | A worker slot; some Wood | Within the first 10 shifts |
| Cleaner | Mixes Water and Chemicals to clean pollution | A worker slot; ongoing Water/Chemicals cost | As soon as pollution shows on the biome |
| Canal / river | Terraforms a waterway that supports biome health | Terraforming effort; some top soil | When a river is feasible on the platform |
| Cold-route planning | Bends the galaxy course away from hot stars | None — a planning step | Before the second space jump |
| Neutral Sector stop | A moderate-climate planet with chickens and cows | One Space Port + Landing Pad setup | When the galaxy map reveals the node |
| Outpost on a cold planet | A second platform in a colder system | One Settlement Ship, one Space Port | Only if Kewa's temperature complaints persist |
The interplay between the rows is what the official beginner guide (linked from the release post and the Hotfix #1 post) covers at a higher level. The above table is the request-specific version: each row either prevents a request, softens the chain that triggers it, or gives the colony a cold backup in case the chain still fires.
Why the pre-emptive playstyle also serves the Peeps
The same moves that pre-empt Kewa's complaints also serve the Peep side. Tree Nurseries spread atmosphere that helps the Peeps stay healthy; Cleaners reduce the toxic tiles that hurt their wellbeing; a cold-route course keeps Peep food and clothing production inside the moderate-temperature band where the Tailor's Warm Weather Clothing and Cold Weather Clothing outputs are most efficient. The Pre-emptive playstyle is not a sacrifice in service of Kewa; it is a single set of moves that solves two linked problems at once. The Kewa happiness guide goes into the Peep side of this loop in more detail.
Space Whales Lore, the Ancestor Connection, and Why Kewa Talks
The lore layer behind the request system is short but explicit. Beyond These Stars is built around your Peeps riding a sentient space whale across a galaxy full of empty planets, alien species, and traces of an older civilisation. The space whales are the carriers, Kewa is the carrier your colony rides, and the Peep Ancestors — the central mystery of the game — are tied into the same galaxy map the colony moves across. The verified lore beats are: Kewa has health and happiness of their own, Kewa speaks to the player, and the galaxy map connects to story events that involve ancestor planets and alien contacts.
A request from Kewa is also, narratively, a request from a being who has decided to keep carrying the colony. Ignoring the request is, in-fiction, a test of whether the Peeps deserve the ride. The developer has not published a hard morality system, a faction approval meter, or a numerical "Kewa trust" stat, but the narrative framing is consistent with the request loop: Kewa asks, the player answers, and the colony either earns the next leg of the journey or relocates to a colder system where the test resets.
| Lore beat | Where it appears in the game | How it ties to a request |
|---|---|---|
| The space whale is sentient | Setting description (store page) | Kewa speaks, so Kewa can ask |
| Kewa has health and happiness | Setting description (store page) | Requests are the UI for those stats |
| The galaxy has alien species | Dev Blog #26 (Ublo) | Alien quests can become resource requests |
| Ancestor planets exist | Dev Blog #28 (galaxy map) | Outpost requests often point at ancestor nodes |
| Kewa can relocate the colony | Dev Blog #29 (emergency travel) | The most extreme kind of request |
The lore layer is also where the game avoids a common pitfall. There is no combat, no enemies, no boss fight, and no PvP in Beyond These Stars — the developer has stated the genres as Simulation and Strategy with no combat tag on Steam. The threat model is environmental: a hot galaxy, a polluted biome, a low-happiness whale. Every request is, mechanically, an environmental warning. A player who reads the lore layer as "Kewa is a friend" will read the requests as "Kewa needs help", and that read is the one the developer has built the dialogue around.
A note on what the developer has joked about but not built
Dev Blog #29 includes a developer joke that an unhappy Kewa will eat the planets the player settled. The post then explicitly says they will not actually do that. The joke is not a mechanic. The verified mechanic remains: an unhappy Kewa triggers emergency travel somewhere cold, and that is the only relocation outcome the developer has published. Players searching for "Beyond These Stars Kewa leaves system" and looking for a punitive outcome will not find one in the official material; the only published outcome is the temperature-driven relocation.
Frequently Asked Questions
What is a Beyond These Stars Kewa request?
A Kewa request is a dialogue prompt the space whale surfaces in response to a variable crossing a threshold — usually temperature, biome health, or production stress. The verified triggers come from Dev Blog #29 (a hot galaxy dragging Kewa's happiness down) and the wider Kewa dialogue system. The player can honour the request, ignore it, or refuse, and the verified consequence of ignoring a temperature request is that Kewa begins emergency travel somewhere cold.
How does Kewa temperature work in Beyond These Stars?
The verified chain is: a hot galaxy lowers Kewa's happiness, a cold galaxy raises it, and a happiness threshold triggers emergency travel. The developer has published the direction of every arrow in that chain but has not published the exact temperature value, the exact happiness number, or the exact threshold. The Neutral Sector, named in Dev Blog #28, is the canonical example of a moderate temperature the player can settle without triggering a temperature complaint.
What is Kewa emergency travel, and when does it trigger?
Emergency travel is the verified response to Kewa's happiness falling far enough. Dev Blog #29 is the only official source, and it states that the destination is somewhere cold. The exact threshold, the exact destination, and the exact shift on which the event fires have not been published. The galaxy map from Dev Blog #28 — partially visible at first, unlocking over time — is the UI the player watches for the course change.
Why did Kewa leave the system in my run?
The verified answer is that the temperature pushed Kewa's happiness past the emergency travel threshold and the request was not addressed in time. The unverified answer — which the developer has not yet published — is the exact number. A practical post-mortem is to check the biome for toxic tiles, check the galaxy map for the course change, and plan a cold-route or Neutral Sector stop on the next leg.
Is there space whales lore that explains the requests?
Yes. The setting description on the Steam store page establishes Kewa as a sentient space whale with their own health and happiness, and the dialogue system is the in-fiction way the whale communicates. The wider Peep Ancestors mystery (Dev Blog #28) and the alien characters (Ublo in Dev Blog #26) layer on top, but the request loop itself is Kewa-to-colony, not ancestor-to-colony.