In Part 1 I covered the six technical problems behind Reiseki's ReAct loop — iteration caps, context management, persistent memory, and security. If you haven't read it, start there . This part is about the design decisions. Even though I had an initial concept in mind, the current layout actually developed over time while testing. I asked the following questions: Who is this for? What should be adjustable by the user and what be automated? And for an agent that has access to your files and remembers your conversations, how can I make this as transparent as possible? Reiseki is open source: github.com/Flo1632/reiseki Two Goals That Pulled in Different Directions Reiseki was designed with two principles in mind that don't always sit comfortably together. The first: it should be usable without any technical knowledge. No terminal, no Python, no config files. If you can install an app, you can run Reiseki. The second: the user should always know what the agent knows about them.…