I'm looking for a news reader app that I can follow news, Reddit, and some keywords if possible. There's so many. What are everyones favorite current apps?
Hi, two week old M5 Air 24 gb latest Tahoe, all up to date. My keyboard is being slow from input/ skipping even. Any suggestions?
Hi, two week old M5 Air 24 gb latest Tahoe, all up to date. My keyboard is being slow from input/ skipping even. Any suggestions?
Bika ai from the AITable .ai original AS is sunsetting to a new platform. I tried to login to this and I am a just a free member. This sucks...
As per their site
For a long time, Bika was never just a product name to us.
It carried many of our core beliefs about the future of work software, and it also carried a very real chapter of our company story.
We wanted software to do more than record work.
We wanted automation to do more than connect steps.
We wanted AI to do more than chat.
We wanted a system that could actually help run work.
That is why this post is not easy to write.
We want to say something clearly:
Bika is not disappearing, but it is entering limited maintenance. Our main product direction is moving to Buda.
This is not a polished positioning sentence. It is the result of a long internal struggle, many attempts to keep pushing Bika forward, and eventually admitting that the future we want to build needs a different foundation.
First, the vision did not change
If we reduce both Bika and Buda to one line, the vision has actually stayed the same:
We were never trying to build just another AI chatbot.
What we wanted was a system that could:
understand context
use tools
execute ongoing work
collaborate with a team
and eventually participate in the daily operation of a company
So this shift is not about abandoning the original idea.
The vision is the same. What changed is the technical path and the product shape.
And eventually we had to admit something difficult:
to achieve that same vision, Bika was no longer the best path forward.
What Bika taught us
If Bika did not exist, Buda would not exist.
Bika was not some failed prelude. It was the stage where we pushed several important ideas far enough to finally see both their power and their limits.
Bika was ambitious by design.
It did not try to solve one tiny workflow. It tried to bring multiple layers of work into one integrated product:
spreadsheets and databases
agents
docs
automation
dashboards
reusable template packages
Our belief was simple: the hardest business problems are rarely solved by a single isolated tool.
Real work usually spans:
data structures
workflows
documents
automation
AI reasoning and generation
So Bika tried to merge them into one template package, so users would not just get features. They would get a full working solution.
We still believe that instinct was right.
And to be direct: Bika is powerful.
If you really go deep into it, it can solve complicated work problems that many traditional SaaS products cannot hold together in one place.
Once you merge spreadsheets, agents, docs, and automation into one system, and then wrap that into reusable template packages, you gain a lot of capability.
But you also create a very real cost:
the interaction model becomes more complex.
A new user is no longer learning one product. They are trying to understand an entire work system.
That creates real friction:
onboarding becomes harder
the mental model becomes heavier
the product becomes less immediately intuitive
the philosophy of the product loses some of its original charm
This was the tradeoff we kept feeling inside Bika.
The capability was real.
But the entry point stopped feeling simple.
And once a product starts feeling like "a very complete and very powerful system that needs to be learned," rather than "an exciting and clear new way to work," something important gets diluted.
There was also a more fundamental issue underneath the product surface.
Bika's agent layer was still largely built around API orchestration.
That works for many useful workflows. It is enough to build a lot of valuable features.
But if you really want an agent to behave more like a long-running employee than a triggered function, you start to hit a wall.
A real agent cannot just be a chain of API calls scheduled from the outside.
It needs its own working environment.
It needs:
its own independent drive
persistent context
its own file system
isolation
a long-running sandbox
a runtime that can actually execute real tasks
That is where Bika had a structural weakness.
It could connect many capabilities, but it was not built from day one around the principle that an agent should own an independent sandbox drive and a persistent place to work.
And over time, we came to believe this was not a nice-to-have.
It was foundational.
Without an independent workspace, an isolated sandbox, and a persistent drive where files, context, and execution traces can accumulate over time, an agent feels less like a real worker and more like a repeatedly invoked capability.
As Bika evolved, it became increasingly clear to us that we did not really want to keep adding AI into an older software shape.
What we wanted was something more radical:
That was the tension we kept wrestling with internally.
Because once you admit that, a lot of the work you could continue doing inside Bika starts drifting away from the future you actually want to build.
That is hard to accept emotionally.
Once you have already spent years building something, you naturally keep asking:
can we just add one more capability?
can we improve the onboarding one more time?
can we finish one more module?
can we postpone admitting that the path itself has changed?
We asked ourselves those questions for a long time.
Why we decided to pivot
Put simply: continuing to invest most of our energy into Bika was no longer the most honest choice.
Not because Bika had no value.
But because we became increasingly certain that the future we actually wanted to build required a different technical base and a different product center of gravity.
That path became Buda.
If we had to summarize the difference in one line:
Bika explored how AI, spreadsheets, docs, and automation could be fused into one powerful work system
Buda is built around an agent-native runtime so an AI Organizer can actually help run a company
This is not just a branding update.
It is a product paradigm shift.
What Buda changes technically
Buda is not a random new story.
It carries forward the deepest beliefs we developed while building Bika, but it narrows the focus and rebuilds from a different technical premise.
If Bika taught us that:
AI should not just chat
automation should not just trigger schedules
systems need memory and context
work software should execute, not just describe work
then Buda asks the next question:
What kind of runtime, workspace, and product architecture do you need if AI is supposed to function like a real team member?
That is why Buda starts from a different place.
It emphasizes:
multi-agent collaboration instead of a single assistant
persistent workspaces instead of disposable sessions
real execution environments like Browser, Terminal, Drive, and Git
team-level orchestration instead of personal experimentation
infrastructure designed for long-running, isolated, manageable agent work
More concretely, Buda is different because:
agents run inside a cloud sandbox, not just through a thin orchestration layer
each agent has its own independent Drive
workspaces are isolated, so agent contexts do not bleed into each other
agents can operate in real execution environments instead of only returning text
the system is built around stronger Coding Agents and Agent Skills
This means Buda feels less like "SaaS with AI added in" and more like an operating environment built for AI workers.
It does not merely support agents.
It first creates independent sandboxes, independent drives, and persistent workspaces, and then lets agents actually live and work inside them.
That difference matters.
This was not an easy decision
From the outside, any pivot can sound like one short sentence:
"The company changed direction."
Inside, it is never that simple.
Usually it means:
admitting that some earlier plans should not continue
accepting that not every previous investment extends cleanly
facing the tension between old users, old pages, old narratives, and a new future
answering the hardest question again: what exactly are we building for now?
For us, the hard part was not coming up with a new name.
The hard part was admitting this:
if we kept treating Bika as the main battlefield, we would not end up where we actually wanted to go.
In startups, the hardest thing is often not making a decision.
It is stopping yourself from continuing the wrong self-justification.
We went through that process.
What this means for Bika users
We do not want to be vague about it.
From this point forward:
Bika is entering limited maintenance
we will prioritize basic stability over expanding the product surface
most new core product investment will go into Buda
This does not mean Bika disappears tomorrow.
It does not mean existing users are suddenly cut off.
But it does mean something important:
if you want to understand where our product direction is going, or where future capability development will happen, you should start looking at Buda.
Why we wanted to say this publicly
We do not want to quietly swap traffic or hide behind vague copy.
If the direction changed, we should explain why.
Users deserve that honesty.
And frankly, we needed to write this for ourselves too.
This is not just a product introduction.
It is a checkpoint.
It is our attempt to:
summarize the past honestly
explain today's tradeoffs clearly
and place a real bet on the future
This post is not about making Bika look worse so Buda can look better.
If anything, the opposite is true.
Bika mattered enough that we felt we owed it a real explanation.
If this resonates, come look at Buda
If you followed Bika all the way here, thank you.
Your feedback, your criticism, and the ways you actually used the product all shaped what Buda became.
And if you care about these questions:
can AI actually do work for a team?
can agents become more than demos?
can future software evolve from tool collections into systems of AI workers?
then we genuinely invite you to take a look at Buda.
Visit Buda
We are not going to pretend the path is perfectly clear.
We do not have every answer.
But we do understand the problem much more clearly now.
Bika got us here.
And the future we want to build now lives in Buda.