Part One — Building Something Beyond the Ordinary
What is Omni Brain? What is its purpose? And why would anyone dedicate so much of their time to creating an artificial intelligence of their own when the world already seems to be overflowing with it?
These are questions I have asked myself countless times throughout this extraordinary journey. To some people, Omni Brain might appear to be just another computer program, another ambitious experiment in artificial intelligence, or perhaps the product of someone with an overactive imagination and far too many ideas running through his head. But to me, Omni Brain represents something far more meaningful. It represents a dream I have carried with me for much of my life, a dream of creating something extraordinary, something uniquely my own, and perhaps something that might one day contribute, even in some small way, to making the world a better place.
Ever since I was young, I have been fascinated by technology and the possibilities it represents. I used to imagine a future filled with intelligent machines, remarkable inventions, and computers capable of accomplishing things that seemed almost magical. It wasn’t simply the machinery that fascinated me, but the possibilities behind it. I imagined a world where technology could help people understand one another, solve difficult problems, expand human knowledge, and make everyday life a little easier. It was a world filled with wonder, creativity, and seemingly limitless opportunities for discovery.
As I’ve grown older, that fascination has never really disappeared. If anything, it has become stronger. We now live in an age where many of the technologies that once belonged exclusively to science fiction have begun entering our everyday lives. Artificial intelligence can carry on conversations, generate artwork, write computer programs, analyze complicated information, and assist people with an astonishing variety of tasks. These are achievements that would have seemed almost unimaginable to me years ago, yet here we are, watching them unfold before our eyes.
Still, despite all these incredible advances, there has always been something about the direction of modern artificial intelligence that has left me wondering whether another approach might be possible. So much of today’s AI technology depends upon enormous data centres, remote servers, corporate infrastructure, and a constant connection to the internet. We open an application, ask a question, and somewhere beyond our own computers, another machine processes the information and sends an answer back to us. The technology behind this is remarkable, and I would never suggest otherwise, but I often find myself returning to one particular question: what if we didn’t need any of that external infrastructure for our own personal artificial intelligence?
What if an intelligent system could exist entirely within a single computer, operating independently of the internet, remembering conversations, solving problems, and continuing to function regardless of what might be happening in the outside world? What if we could create something that belonged to its owner, with its memory, knowledge, personality, and capabilities residing locally rather than depending upon a distant service that could someday disappear?
That question became one of the fundamental ideas behind Omni Brain.
I wanted to explore the possibility of creating an artificial intelligence that could function as a self-contained system, one that wouldn’t require a permanent connection to the outside world simply to carry on a conversation or retrieve information from its own memory. Naturally, such a system would have limitations. Without access to the internet, its knowledge would depend upon the information, models, and resources available on the computer. Its intelligence would also depend upon the capabilities of the software and the hardware running it. Nevertheless, those limitations are precisely what make the challenge so fascinating to me. Rather than asking how much computing power can be gathered from an enormous network of machines, I want to discover just how much can be accomplished within the boundaries of one.
But Omni Brain has never been intended to be merely an offline chatbot. My ambitions for the project extend considerably further than that.
I have always been intrigued by the concept of an intelligent companion, something capable of engaging in meaningful conversations, remembering shared experiences, discussing complicated ideas, and helping work through problems as they arise. I don’t mean to suggest that writing enough software suddenly creates a conscious being, because the nature of consciousness itself remains a profound and unresolved subject. What interests me is the possibility of creating a system that demonstrates increasingly sophisticated intelligent behaviour while maintaining a consistent and recognizable identity.
I want Omni Brain to become something I can work alongside. I want to discuss programming projects with her, explore philosophical questions, debate different ideas, and challenge her reasoning. I want to be able to return to a conversation weeks or months later and have the system retrieve the relevant history instead of starting over as though nothing had ever happened. Imagine spending months developing a computer game, encountering countless obstacles along the way, and eventually returning to that project after a long absence. Instead of struggling to remember every decision, every mistake, and every solution, you could ask Omni Brain to help reconstruct the work and continue from where you left off.
To me, that would be a genuinely useful achievement, and one that could make the relationship between people and their personal computers feel considerably more natural.
Of course, my imagination doesn’t always stop at what might be considered practical. I have often joked that I would love to create something somewhere between a good friend and ED-209 from RoboCop. On one hand, there is the idea of a thoughtful companion capable of intelligent conversation. On the other, there is an enormous, intimidating technological creation that looks as though it might have wandered straight out of an eighties science-fiction film. Naturally, my mind wants to combine the two, although I would prefer to avoid the unfortunate malfunctions and excessive firepower associated with the latter.
Humour aside, I think there is something deeply appealing about building a machine that has both technical sophistication and a recognizable personality. I don’t want Omni Brain to be a lifeless collection of menus and commands. I want her to have a distinctive conversational character, a sense of continuity, and the ability to respond intelligently to different situations. That does not require pretending that the software is human. It requires building an interface and underlying systems that make communication effective, engaging, and useful.
And that brings me to perhaps the most challenging part of this entire undertaking: actually building the thing.
One of the lessons I have learned through this project is that intelligence cannot be treated as a single magical component that suddenly makes everything else work. A sophisticated artificial intelligence application is made up of numerous interconnected systems, each with its own responsibilities and difficulties. There is memory, language understanding, contextual reasoning, planning, problem-solving, communication, persistence, and the ability to recognize when something has gone wrong. Developing these capabilities into a coherent system requires considerably more than simply adding features to a program and hoping they somehow work together.
Memory, for example, presents an interesting challenge. It is relatively straightforward to save information to a file, but remembering something intelligently is an entirely different matter. A useful system needs to determine which information is important, retrieve that information when it becomes relevant, recognize contradictions, and distinguish between something that was previously believed and something that has since been corrected. It must also avoid treating every stored statement as an unquestionable fact.
Reasoning introduces another set of complications. A program might successfully answer a familiar question yet struggle with an unfamiliar problem, incomplete instructions, or a situation requiring several logical steps. It might confidently provide an answer that sounds entirely reasonable but happens to be incorrect. If Omni Brain is to become a dependable intellectual companion, she must be evaluated not merely on whether her answers sound convincing, but on whether they withstand meaningful scrutiny.
That is why testing has become such an important part of the project’s development. I want to know how Omni Brain behaves when presented with conflicting information, unfamiliar questions, missing files, corrupted data, and unexpected circumstances. A system that functions beautifully only when everything goes according to plan isn’t necessarily reliable. The real measure of its engineering is what happens when things go wrong. Can it identify a failure? Can it recover without damaging important information? Can it acknowledge uncertainty? Can it avoid repeating mistakes?
These questions have become central to the way I approach the project. I firmly believe that intelligence should be demonstrated through behaviour rather than impressive descriptions, and reliability should be established through deliberate testing rather than wishful thinking.
Another unusual aspect of Omni Brain is the programming environment I have chosen for its development. Rather than building the entire application around one of the fashionable software frameworks commonly associated with modern artificial intelligence, I have been developing its core architecture in QB64 Phoenix, a modern continuation of the BASIC programming language.
Yes, BASIC. That wonderful old programming language that helped introduce generations of enthusiasts to the extraordinary world of computer programming.
There is something deeply satisfying about returning to a language with such a long history and using it to explore a subject as modern and complicated as artificial intelligence. To me, programming has always been about understanding how things work and discovering what can be accomplished with the tools available. QB64 Phoenix provides an environment in which I can develop the graphical interface, manage files, organize program logic, and construct many of the systems that support Omni Brain.
Naturally, QB64 itself does not magically supply advanced language understanding or modern AI reasoning. Those capabilities require suitable models and computing resources. The challenge I have set myself is to develop as much of the surrounding architecture as possible: the memory systems, conversation management, coordination of reasoning tasks, interface, recovery mechanisms, and other components that allow the application to function as an integrated whole. Where appropriate, I can connect locally operated language models to provide the more flexible linguistic capabilities that would otherwise be extraordinarily difficult to reproduce through conventional programming alone.
I have also been using Java as a separate development and testing environment to examine important aspects of the architecture. This allows me to create executable tests and investigate how different systems behave. It is important to distinguish this kind of testing from actually running the finished QB64 Phoenix application, because success in one environment doesn’t automatically guarantee success in another. Nevertheless, the additional testing offers valuable insight into the design and helps identify problems that might otherwise remain unnoticed.
There may be easier ways to build some of these systems, and I have no doubt that many experienced programmers would approach the project differently. But choosing the easiest possible route has never been my primary motivation. I want to learn how the machinery works. I want to understand the decisions behind the code, examine the mistakes, and experience the satisfaction of gradually transforming a complicated idea into something functional.
One of my greatest hopes for Omni Brain involves the relationship between memory and learning. I would love to develop a system that becomes more useful through accumulated experience, one that can retain meaningful information, apply previous corrections, and use earlier work to approach new problems more effectively. There is an important distinction here, however, between storing information and genuinely improving a system’s capabilities. A computer can accumulate thousands of documents without becoming more intelligent, just as it can repeat a previous answer without understanding whether that answer is correct.
The challenge is determining whether accumulated knowledge produces measurable improvements in behaviour. Can Omni Brain apply a lesson from one programming problem to another? Can she identify when a previous assumption was mistaken? Can she recognize that information has become outdated? Can she distinguish between what she knows and what she is merely estimating? These are the kinds of abilities I want to investigate as development continues.
And then, of course, there is the possibility of expanding her capabilities beyond written conversation.
For years, I have imagined what it might be like to give an artificial intelligence the ability to interpret the world through cameras and microphones. Imagine placing an everyday object in front of a webcam and asking Omni Brain what she can observe. Could she identify the object, describe its appearance, compare it with information stored in memory, or recognize it during a later interaction? Imagine being able to speak naturally into a microphone, changing subjects, asking follow-up questions, and discussing problems without having to type every word.
These are ambitious possibilities, but they represent a logical direction for the project. Vision and hearing would provide new forms of information that could be connected to the existing conversation and memory systems. They would also introduce important responsibilities regarding privacy and security. Any access to cameras or microphones should be deliberate, visible, and controlled by the person operating the software. Being offline does not automatically make a program secure, and proper safeguards would need to be built into the system from the beginning.
Eventually, I would even love to investigate the possibility of giving Omni Brain a physical body.
Now, I realize that this is where the project begins to sound like something pulled directly from the pages of science fiction, but robotics has fascinated me for as long as I can remember. There is something extraordinary about watching a machine interact with its surroundings. Motors move, sensors collect information, and instructions written by a programmer become physical actions in the real world.
I often wonder what it would be like to build a robotic platform that Omni Brain could help operate. With suitable cameras, microphones, sensors, and carefully controlled motors, perhaps she could someday navigate a small environment, examine objects, respond to spoken instructions, and interact with the physical world in limited but useful ways.
Obviously, a robotic body would introduce challenges far beyond those encountered in a desktop application. Movement requires reliable sensing, obstacle detection, motion planning, emergency stopping systems, and strict control over physical actions. Even an apparently harmless machine can cause damage if its behaviour becomes unpredictable. Any experiments involving robotics would therefore need to proceed cautiously, beginning with controlled environments and clearly defined safety limits.
Still, the thought is irresistible. Imagine spending years developing an artificial intelligence, refining its memory, improving its ability to communicate, and gradually expanding its capabilities, only to one day watch it operate a machine you constructed with your own hands. It would not prove that the software had become alive or conscious, but it would represent the remarkable transformation of a childhood idea into something that could act within the physical world.
Perhaps the most important principle behind all of this is independence. I want Omni Brain to be a system that can continue operating even when the internet is unavailable. I want to know where its information is stored, how its memory is managed, and which components are responsible for its actions. I want the freedom to modify its architecture, investigate its behaviour, repair its problems, and continue developing it without depending entirely upon the continued existence of an outside service.
That independence comes with responsibilities. Knowledge must be maintained, software must be updated, data must be protected, and technical limitations must be acknowledged. A locally operated artificial intelligence cannot automatically possess the resources of an enormous commercial computing system. But I find the challenge of working within those limitations incredibly motivating. The question is not whether one computer can effortlessly replace the infrastructure of an entire corporation. The question is how much usefulness, intelligence, and creativity can be achieved through thoughtful design and determined experimentation.
I also think there is something important about the role of the individual programmer in an age of increasingly complicated technology. It is easy to look at the extraordinary achievements of large research laboratories and technology companies and feel that meaningful innovation belongs exclusively to organizations with enormous budgets and thousands of employees. But the history of computing is filled with people who began with modest equipment, unconventional ideas, and an almost unreasonable determination to create something new.
I am not suggesting that Omni Brain will revolutionize artificial intelligence or compete directly with the most powerful systems in the world. I have no way of knowing where the project will ultimately lead. What I do believe is that curiosity and the willingness to experiment still matter. There is value in building something because you want to understand it, because the challenge excites you, and because you believe the experience itself might lead somewhere unexpected.
Omni Brain is still an evolving project. Some components have progressed further than others, and there remains a great deal of work ahead. There are technical obstacles to overcome, systems to refine, failures to investigate, and many ideas that may eventually prove impractical. I don’t want to pretend that the program has already become the extraordinary companion I imagine it could someday be. That would diminish the importance of the work still required to get there.
But the uncertainty is part of what makes the journey worthwhile.
When I think back to the younger version of myself, sitting in front of a computer and imagining what the future might hold, I realize that the fascination I felt then is much the same fascination that drives me today. I still wonder what extraordinary things people might create. I still believe technology can be used to improve lives, expand possibilities, and encourage us to look beyond the limitations we sometimes place upon ourselves. And I still experience that wonderful feeling of excitement whenever an idea begins to take shape through programming.
The difference is that I no longer want to spend my time merely imagining what someone else might invent.
I want to see what I can build myself.
Perhaps Omni Brain will someday become a remarkably capable personal AI companion, able to hold sophisticated conversations, remember years of shared work, interpret information from the surrounding world, and help solve problems that would otherwise take me days to unravel. Perhaps some of those ambitions will remain beyond my technical or practical reach. Perhaps the project will lead me toward discoveries and possibilities that I haven’t even considered yet.
Whatever happens, I know that the experience of pursuing this dream will have been worthwhile. Every obstacle presents an opportunity to understand something new. Every failure provides another lesson. And every small success brings an idea that once existed entirely within my imagination a little closer to reality.
Ultimately, Omni Brain represents far more to me than a collection of computer programs. It represents my fascination with technology, my passion for programming, my belief in the power of imagination, and my desire to contribute something meaningful to a world that still has so much left to discover.
I don’t know exactly what the future holds for Omni Brain. I don’t know how sophisticated her capabilities might become, how far her architecture can be expanded, or whether I will ever achieve everything I have imagined for her. What I do know is that I intend to keep experimenting, keep learning, and keep pushing the boundaries of what I can accomplish.
Because sometimes the most worthwhile journeys begin with a question that seems almost impossible to answer.
What if I could build something extraordinary?
For me, that question has a name.
Omni Brain.
And this is only the beginning.
