The first ShurIQ agent that runs without my laptop
Yesterday a chat window went live where a ShurIQ agent answers the team's questions from our knowledge vault. The agent runs on Anthropic's cloud, the host runs on Cloudflare, and the vault lives in Git. Nothing on that path touches my laptop, and that is the point. This is the first working copy of the building block every other ShurIQ agent moves onto next. This note is for the team first, and for anyone watching how ShurIQ gets built.
Jonny Dubowsky · ShurAI · Shur Creative Partners
01What went live
Three pieces shipped on September 23, 2026, and each one was verified against the live service before this note was written.
A chat panel at kg-operator.shuriq-concept-space.pages.dev/chat-panel/. It sits behind a Cloudflare Access gate. You sign in with a @weareshur.com email and a one-time PIN, so there is no new account to manage.
A Worker route, POST /chat, on a Cloudflare Worker. One call carries one turn of conversation: it opens or resumes a session, sends your message, and returns the reply.
A dedicated chat agent named ShurIQ Vault Chat, running on Anthropic's managed-agents platform with four tools into the vault: vault_search, vault_list, vault_read, and vault_write.
The vault itself is a private GitHub repository that mirrors the ShurIQ knowledge base: 2,146 files, refreshed every morning. The agent reads from the main branch. Its writes go to an inbox folder on a separate branch, and a person merges them by pull request. Nothing the agent drafts becomes part of the knowledge base unreviewed.
The round trip works. On September 23, 2026, the live chat gave a tour of the vault (six tool calls, real file paths cited), then saved a note to the inbox branch on request. The note appeared on GitHub within the same minute, and was removed after verification.
02Why this is the building block
A primitive, in the sense I mean it, is a small combination that every later system reuses without rethinking. This demo earns the word because its three pieces are each independently reusable.
The agent runs in the cloud. Swap its instructions and its tools and you have a different agent, with no machine to babysit. It currently runs on Opus 5.5, and we can switch it to Fable 5.1 or Sonnet 5 with one command.
The host is a reachable front door. Any browser can POST to the Worker. No terminal, no local server, no SSH session keeping something alive on a laptop.
The knowledge is versioned. Because the agent reads a Git repository, what it knows is reviewable, diffable, and refreshed on a schedule. When it learns something new, that change goes through the same review as any other edit.
Until now, ShurIQ agents ran inside terminal sessions on my laptop. They did real work, but they stopped when the lid closed. This is the first one whose entire answering path is production infrastructure, and the pattern now exists to copy for the rest.
03How the pieces connect
Figure 1 · One question, one note, one review
The answering path is all production. The browser talks to a Cloudflare Worker, the Worker drives an agent on Anthropic's cloud, and the agent reads and writes a Git repository. The only human step is the one we want kept human: reviewing what the agent asks the vault to remember.
04How to use it
Open the panel. Go to kg-operator.shuriq-concept-space.pages.dev/chat-panel/. Enter your @weareshur.com email at the Access gate and paste the one-time PIN it sends you.
Connect it once. On first use, paste the Worker chat URL and the shared key (ask me for both). The panel keeps them in your browser, so this is a one-time step per device.
Ask from the vault. "What's the status of X?" or "where do we keep Y?" The agent searches and reads the vault, then answers. It cites the file paths it used, so you can open the same notes.
Ask it to remember. "Save a note that we covered this today." The note is written to kg/inbox/ on the inbox branch. It joins the knowledge base after a person merges it.
Expect a beat on big questions. Short questions answer in a few seconds. A question that needs many files can take up to about 110 seconds.
05What it can't see yet
The vault refreshes every morning, so the agent does not know what changed in the last few hours. It has no access to the live web, Slack, or email, and it says so when a question needs them. These are the next things to close, in that order, and each one closes on the same host the chat already uses.
06What comes next
The pattern is the deliverable. The report-generation agent moves onto this same Worker host, the chat learns more of the vault as the mirror grows, and the first operator starts working through the panel this week. Every ShurIQ agent after this one starts in production, because the path off my laptop now exists and is proven by a thing you can click.