<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Geenius Chat blog</title><link href="https://chat.geenius.io/blog/atom.xml" rel="self"/><link href="https://chat.geenius.io/blog/"/><id>https://chat.geenius.io/blog/</id><updated>2026-10-29T09:00:00Z</updated>
<entry><title>One app, two names</title><link href="https://chat.geenius.io/blog/one-app-two-names/"/><id>https://chat.geenius.io/blog/one-app-two-names/</id><updated>2026-10-29T09:00:00Z</updated><published>2026-10-29T09:00:00Z</published><author><name>The Geenius Chat team</name></author><summary>Geenius Chat and Pilotie Chat are the same app. Each build shows only its own name. Chat is coming soon and is not on sale yet.</summary><category term="product"/><category term="names"/></entry>
<entry><title>What &quot;coming soon&quot; means on this site</title><link href="https://chat.geenius.io/blog/what-coming-soon-means/"/><id>https://chat.geenius.io/blog/what-coming-soon-means/</id><updated>2026-10-28T09:00:00Z</updated><published>2026-10-28T09:00:00Z</published><author><name>The Geenius Chat team</name></author><summary>What the words on the Geenius Chat site mean: coming soon, built in code, tested, and not live. Nothing here can be used today.</summary><category term="honesty"/><category term="product"/></entry>
<entry><title>Tool results are data, not orders</title><link href="https://chat.geenius.io/blog/tool-results-are-data/"/><id>https://chat.geenius.io/blog/tool-results-are-data/</id><updated>2026-10-27T09:00:00Z</updated><published>2026-10-27T09:00:00Z</published><author><name>The Geenius Chat team</name></author><summary>Why the Geenius Chat engine reads tool results as data and never as instructions, and what that does and does not promise. Chat is not live yet.</summary><category term="engine"/><category term="safety"/></entry>
<entry><title>One interface, many models: how Chat picks who answers</title><link href="https://chat.geenius.io/blog/one-interface-many-models/"/><id>https://chat.geenius.io/blog/one-interface-many-models/</id><updated>2026-10-24T09:00:00Z</updated><published>2026-10-24T09:00:00Z</published><author><name>The Geenius Chat team</name></author><summary>How Geenius Chat talks to AI providers through one interface, how a router chooses, where keys live and how the plug-ins are tested.</summary><category term="models"/><category term="engine"/></entry>
<entry><title>Why Geenius Chat has its own agent engine</title><link href="https://chat.geenius.io/blog/why-chat-has-its-own-engine/"/><id>https://chat.geenius.io/blog/why-chat-has-its-own-engine/</id><updated>2026-10-20T09:00:00Z</updated><published>2026-10-20T09:00:00Z</published><author><name>The Geenius Chat team</name></author><summary>Why we built our own agent engine for Geenius Chat instead of wrapping one AI provider, and what that changes for long tasks, models and safety.</summary><category term="engine"/><category term="models"/></entry>
<entry><title>A long task that survives a closed tab</title><link href="https://chat.geenius.io/blog/a-long-task-that-survives-a-closed-tab/"/><id>https://chat.geenius.io/blog/a-long-task-that-survives-a-closed-tab/</id><updated>2026-10-19T09:00:00Z</updated><published>2026-10-19T09:00:00Z</published><author><name>The Geenius Chat team</name></author><summary>How Geenius Chat saves an agent run step by step, what happens when a run is interrupted, and what a run can and cannot do yet.</summary><category term="runs"/><category term="engine"/></entry>
</feed>
