Introducing Busabase V1.0

Released: October 29, 2026

Over the past few months, we have kept coming back to one question: When you start using multiple AI Agents, how can the work they have done become the starting point for what comes next?

A piece of research stays in a chat. A way of working lives in a project directory. Customer records sit in another tool. Switch Agents, and you often have to find the materials again, explain the background, and move the results to where your team actually works.

Busabase began by making Agent writes reviewable and traceable, then gradually brought bases, documents, files, skills, and apps into one workspace. Today, you can connect Busabase from Agent platforms including Muse, Grok Bot, Claude Code, Codex, and WorkBuddy, read shared materials, and write new results back.

Today, we are officially releasing Busabase 1.0.

This is more than a version number change. It marks a complete loop for the core way of working we originally envisioned: connect the Agent you prefer, read shared knowledge and working methods, complete a task, and leave the results behind. When needed, people review the changes before the team, an app, or the next Agent carries on.

Different Agents. The same context. Changing tools should not mean starting over.

✨ New Features

1.0 is a milestone in months of continuous development. Not all of the capabilities below are new in this release; together, they make up the Busabase you can use today.

• Bring multiple Agents together around shared work: Busabase does not ask you to replace the Agents you already use. It gives them a shared workspace to read from and write to. Through Agent Skills, MCP, CLI, or APIs suited to each environment, different Agents can read the same records, documents, and playbooks within their permissions, then leave results for the next task.

• Turn chat results into data you can keep maintaining: Use bases to organize customers, projects, content, and research into structured records, then present the same data in tables, boards, calendars, and galleries. Relations, lookups, formulas, filters, and forms let Agents do more than deliver an answer: they can help maintain business information that keeps evolving.

• Turn one-off attachments into a knowledge base for people and Agents: Documents, Drive, and files live alongside bases in the same workspace, so project briefs, source materials, and deliverables no longer need to be scattered across tools. People can read, preview, and search directly, while Agents can find and read relevant content, keeping conclusions together with the materials that support them.

• Turn repeated instructions into shared ways of working: Save field definitions, writing requirements, customer follow-up processes, and more as Skills and custom prompts, then find and reuse them in Playbooks. Your methods stay with the workspace instead of living only in one Agent's configuration. Switch Agents, and the same instructions are still there to read.

• Go from saving results to building apps with them: AirApp lets Agents build customer workbenches, content management interfaces, or business dashboards around workspace data for people to use in Busabase. Templates bring data structures, example content, playbooks, and optional app interfaces into the workspace together. After installation, you can keep working through conversations with an Agent and adapt the data and apps as your needs change.

• Keep automation fast and accountable: Writes leave explanations, diffs, and history through Change Requests. With write access, changes can take effect directly; when human review is needed, they go to the Inbox. Inspect the changes, give feedback, approve, or reject them, keeping both efficiency and control over important decisions.

• Choose the deployment that fits, with the same way of working: From the local open-source edition to self-hosting and Busabase Cloud, choose an option that suits your data location, operations, and team collaboration needs. Whichever you choose, the core is the same: people and Agents working with shared data, knowledge, skills, and apps.

For example, Claude Code can organize project research into documents and records, then Codex can read those materials to draft an execution plan. Your team reviews important changes in Busabase, follows progress through a board or AirApp, and passes new requirements to an Agent. What is shared is not the chat history from different platforms, but the working context you choose to save in Busabase and keep reading and maintaining.

🔧 Improvements

In the final week leading up to 1.0, we continued refining this workflow: less repeated explanation, easier handoffs, and a smoother experience whenever you open the workspace.

• Space instructions preserve the shared background every task needs: Administrators can maintain the team's vision, values, design style, and general requirements in space settings, where members can read them. Connection guidance instructs Agents to read the latest space instructions at the start of a new task, then look for applicable playbooks, so you do not have to explain the team background from scratch each time.

• Hand the current content to an Agent in one step: Use Copy location, Copy for Agent in the sidebar, or a keyboard shortcut to include the current content's location and connection guidance. The updated Busabase Skill also recognizes workspace links as task targets and reads materials through the configured connection, reducing cases where an Agent opens a web page and gets stuck at sign-in.

• See and choose the context in your chat: Current-page references, files, and prompts appear as compact context tags. Check or remove them before sending, and look back at what you provided afterward. Type / in chat to select a Skill you can access in the current space, rather than being limited to the Agent's built-in commands.

• See more clearly what your Agent is doing: Sessions connected through Buda can show plans, tool operations, file changes, and questions that need your answer, then retain the final result. Supported models also let you choose a thinking level in the model menu. Connection details, custom names, and information about who actually connected make it easier for the team to tell which Agent is in use.

• Put related data to work together: Two-way relations can be edited from either side. Lookup fields and formulas that depend on them use the source data you can currently see, and views support combined AND/OR conditions. Customers and opportunities, or projects and tasks, become more than links to each other: you can query, calculate, and follow up on them together. Tables and boards with many relations also spend less time loading items one by one.

• Check records and files without losing your place: Open records from tables, boards, and calendars in a detail dialog, making it easier to return to your original position in the list. Boards can show attachment thumbnails and use images as covers. File previews now support STL, OBJ, glTF, and GLB 3D models, and long Word documents are easier to open.

• Deliver results beyond the workspace more easily: Publicly shared folders retain their directory structure and breadcrumbs, so recipients can keep browsing within the shared scope instead of opening an isolated page. Temporary read-only links created through an Agent, CLI, or API can have an expiration of up to seven days, making them useful for delivering reports, records, and content awaiting review.

🐛 Bug Fixes

Alongside these capabilities, we focused on details that could interrupt everyday work.

• Save status matches the actual result: Fixed whiteboards, HTML, and workflows incorrectly reporting Saved when editing continued during a save. Pending review and applied changes are clearly distinguished, and drafts with subsequent edits are preserved.
• Explicit review requests wait for review: Fixed some Agent operations losing the choice to submit for review first, which could apply changes immediately when write access was available. Operations without an explicit review request still follow existing permissions.
• Switch spaces without bringing the previous session along: The Agent panel is isolated by workspace and user. Chat tabs and the active session from another space no longer linger after switching.
• New fields and view settings no longer overwrite each other: Fields added from a view appear according to that view's display rules. Changing only column widths, filters, or names no longer submits stale field visibility settings, and background updates no longer unexpectedly reset drafts you are editing.
• Search results better reflect the current workspace: Closed Change Requests no longer cause normal records to appear twice, and deleted or archived content no longer gets in the way through stale search caches.
• More reliable WorkBuddy connections: Added the authorization callback used by WorkBuddy's custom MCP connectors, reducing incorrectly rejected client connections.
• Connecting from a space-specific address no longer incorrectly reports expired authorization: Fixed authorization issues when connecting Buda or ACPRouter from a space subdomain, and improved status messages for cancellation, retries, and parallel connections.
• Email invitations take you to the right space: Joining through an email invitation opens the intended space. If the invitation has expired, been canceled, or does not exist, a clear message asks you to contact the inviter for a new one.

---

1.0 is not the end of iteration. It is a starting point you can keep building on.

Thank you to everyone who has used Busabase, shared feedback, and helped shape it over the past few months. The real work you entrusted to Agents has brought this product from its original idea to where it is today.

Your next task does not have to start from a blank page. Connect the Agent you prefer to Busabase and carry on with the knowledge, data, and ways of working you have already built up.

Connect your Agent · Choose a template · Read the getting-started guide