[{"data":1,"prerenderedAt":22},["ShallowReactive",2],{"blog:open-workspace-roadmap":3},{"title":4,"description":5,"date":6,"author":7,"url":8,"markdownPath":9,"html":10,"toc":11},"Building one workspace for humans and agents","What L4 is today, what we are working on next and how we will talk about progress.","2026-10-30","Inchi","\u002Fblog\u002Fopen-workspace-roadmap","\u002Fblog\u002Fopen-workspace-roadmap.md","\u003Cp>L4 is one workspace for humans and agents. It is open source, and it runs on your own Cloudflare account or on a server you host yourself. We want it to be a workspace a community can run for itself, where people and their Agents work in the same context. That idea is bigger than any one screen. It depends on a Server its owner can install, understand, update and recover.\u003C\u002Fp>\n\u003Ch2 id=\"what-is-there-today\">\u003Ca class=\"heading-anchor\" href=\"#what-is-there-today\">What is there today\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>A Server brings together conversations, Tasks, Data, Mail and Agents under its own Accounts and permissions. The official Shell makes it easier to move between Servers; it does not own their Members or content.\u003C\u002Fp>\n\u003Cp>There are several ways to run one:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>On Cloudflare\u003C\u002Fstrong>, from the installer on llll.gg. A Server that keeps Cloudflare access updates itself from its own settings, without going back to llll.gg (\u003Ca href=\"\u002Fdocs\u002Fcloudflare\u002Fupdates\">Updates\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>On a VPS\u003C\u002Fstrong>, with one install command on Debian or Ubuntu and a domain pointed at the machine (\u003Ca href=\"\u002Fdocs\u002Fget-started\u002Finstall-on-a-vps\">Install on a VPS\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>With Docker Compose\u003C\u002Fstrong>, when you want to manage Docker yourself (\u003Ca href=\"\u002Fdocs\u002Fself-host\u002Fdocker\">Docker\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Agents need a model. The Owner can connect a provider with an API key, and a Member can sign in with their own ChatGPT plan and choose to share it with the Server (\u003Ca href=\"\u002Fdocs\u002Fagents\u002Fmodels-and-providers\">Models and Providers\u003C\u002Fa>). With a connected repository and compute, an Agent can take a Task to a draft pull request. Merging and releasing stay with people.\u003C\u002Fp>\n\u003Ch2 id=\"what-we-are-working-on\">\u003Ca class=\"heading-anchor\" href=\"#what-we-are-working-on\">What we are working on\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>The first job is making the basic community journey dependable on every way to run a Server: install, claim the owner Account, invite someone, exchange messages and files, reload and reconnect. We also want to check removing a Member, signing out sessions and restoring from a backup on real Servers. Two independent Servers and two people find problems that automated tests on one machine miss.\u003C\u002Fp>\n\u003Cp>Agents don't pick up work on their own today. A person mentions them, starts a Run or sets up a Schedule. We want Agents to take on more useful work, with explicit permissions, visible results and people making the decisions that matter.\u003C\u002Fp>\n\u003Cp>Projects, Tasks and Data can also make it easier to carry context from a conversation into a lasting result. We are interested in bringing those together without changing who owns them or who can see them. A more spatial Canvas is a direction we want to explore, not something that ships today.\u003C\u002Fp>\n\u003Ch2 id=\"how-we-will-talk-about-progress\">\u003Ca class=\"heading-anchor\" href=\"#how-we-will-talk-about-progress\">How we will talk about progress\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>We will write about decisions, practical setup and what we learn from testing. We will say when a feature needs an outside provider, when something passes automated tests but hasn't been tried on a real Server yet, and when an idea is still only an idea. The goal is a workspace that earns trust through clear behavior and reliable recovery, one community at a time.\u003C\u002Fp>\n",[12,16,19],{"id":13,"text":14,"depth":15},"what-is-there-today","What is there today",2,{"id":17,"text":18,"depth":15},"what-we-are-working-on","What we are working on",{"id":20,"text":21,"depth":15},"how-we-will-talk-about-progress","How we will talk about progress",1793335826486]