The words AI tools use
Hiveku AI
Hiveku AI, the chat in the editor, works on the branch the editor is on. The editor decides which branch a request works on, never the AI.- Its edits land on the branch you are working on, and each request is saved as one version (“Saved automatically after an AI request”).
- Chatting on a branch needs Websites › Deployments: Manage. A chat belongs to the branch it started on: switch back to that branch to carry on with it.
- It asks you first with an approval card in the chat before it merges a branch or a review, adds a review to the merge line (never as urgent), moves a review to another branch, shows a branch on Development or Staging, deletes a branch, moves changes that are not live yet to a branch, rolls back, or deploys.
- It goes ahead without a card to read branches, versions, reviews and the merge line; start a branch; restore an archived branch; open, close, decline and reopen reviews; comment and ask for changes (it never approves); resolve conflicts on the branch it is working on; and start or stop a branch preview.
- A few tools refuse on a branch because they change Your site directly, such as syncing universal components, adding from the section library, the redesign tools, and deleting, moving or optimizing images: “This tool changes your site directly, so it can’t run while you’re working on the branch name.”
- In plan mode it changes nothing.
Outside AI tools
Outside AI tools (the Claude Code plugin, Codex, the VS Code extension, Hiveku Sync, and AI apps connected to Hiveku such as claude.ai and ChatGPT) connect with a person’s own Hiveku key. Each call can do only what that person can do in the dashboard: a key whose creator can only read the site is read-only. What no AI tool can do, whatever its key:- approve a review (
403 approval_needs_person) - change Branch settings
- dismiss someone else’s review, or edit or delete someone else’s comment
- put a review at the front of the merge line, unless the key’s creator is an owner or admin
- approve its own request on a merge-line approval link
Claude Code plugin
Whatever your Claude Code settings say, the plugin always asks before it saves a version with files, applies a rollback, resolves conflicts, or adds a review to the merge line. The ask list in its install guide also covers deploys, merges, environment changes, deleting branches, moving changes to a branch, editing a review, and restores.
The plugin tells Hiveku that it asks you first, so on a site that requires reviews for outside AI tools, it adds reviews to the merge line after its own question, with no approval link. See Claude Code plugin.
Codex
The Codex plugin’s hiveku-ship skill covers the whole flow: save, check, version, deploy, roll back, branches, reviews, conflicts and the merge line. Codex asks before it deploys, saves several files at once, saves a version, merges, resolves conflicts, rolls back, edits a review, adds a review to the merge line, changes an environment, deletes a branch, moves changes to a branch, or restores. Everything else runs without asking, including saving or deleting a single file, creating branches, opening, closing and reopening reviews, comments, and taking a review out of the merge line.VS Code extension
The extension works from the Source Control view, the status bar (which shows the branch your folder tracks) and the command palette. It uses developer words: “pull request” for a review, “commit” for a version.
VS Code has no merge line, and it cannot approve or post reviews: Open in the dashboard takes you there. A merge refused for conflicts offers Resolve in the dashboard, or Resolve here to keep one side per file, then Merge again. A change to an archived branch offers Restore branch.
In folders it sets up, the extension also adds Claude Code commands (
/hiveku-branch, /hiveku-pr, /hiveku-commit, /hiveku-rollback and more) that ask before a rollback, resolving conflicts, or adding to the merge line.
AI apps connected to Hiveku
AI apps connected through Hiveku’s connector, such as claude.ai and ChatGPT, use the same tools. Their apps do not ask you before adding a review to the merge line, so on a site that requires reviews for outside AI tools, Hiveku sends them an approval link to give you instead.The tools
Versions and status
Branches
Merging and conflicts
Reviews
The merge line and settings
Environments, previews and builds
The file tools take
branch too: project_files_bulk_get, project_files_bulk_save, project_file_get, project_file_save and project_file_delete. Leave it out, or pass main, to work on Your site. project_files_status accepts target: "branch:<name>".
The checks verify_typecheck, verify_lint and verify_run_tests run in Your site’s preview only.
When a tool is refused
Working on a shared site
When several people and AI tools work on one site:- Read the merge line (
project_vcs_queue) and the open reviews before you start. - Start a branch for each piece of work, and save on it by name.
- Record
working_tree_etagfromproject_vcs_brancheswhen you read, and check it again before you write, to catch changes made meanwhile. - Open a review and add it to the merge line. Joining is the approval to merge, so ask the person first.
- Publishing is a separate step. Merging never puts anything live.