Annex — Antigravity 2.0 (Google)

This guide covers integrating KaKeKiKoKu with Antigravity 2.0, Google's standalone desktop command center for agent projects.

Antigravity 2.0 is no longer simply the old VS Code-based Agent Manager. Google now separates four surfaces: the standalone Antigravity 2.0 app, Antigravity CLI, Antigravity SDK, and Antigravity IDE. This page uses the standalone 2.0 app as the primary path while preserving the workspace configuration needed by IDE and CLI users.

Antigravity projects can contain one or several folders and can work directly in local folders or isolated Git worktrees. KaKeKiKoKu remains attached to the real project paths it has opened, so use Local mode for the simplest first verification.

This guide covers Windows and Linux. Linux installs KaKeKiKoKu from the Snap Store and has been validated with Antigravity.

Antigravity does not support KaKeKiKoKu channels today. KaKeKiKoKu therefore works in Precise mode: the selected Antigravity model can use KaKeKiKoKu MCP tools, while KaKeKiKoKu UI actions that would push messages to the AI copy text to the clipboard for you to paste.

Requirements

Before you start the KaKeKiKoKu integration flow, you need:

• KaKeKiKoKu installed — Windows and Linux instructions are on the Download page. Linux installs from the Snap Store.
• Antigravity 2.0 installed or updated — use Google's official Antigravity 2.0 product page.
• An active Google account with access to Antigravity. KaKeKiKoKu works through the agent and reasoning model Antigravity already orchestrates; it does not consume the Google API directly.

Install or update Antigravity

Use Google's official download page:

https://antigravity.google/product/antigravity-2?app=antigravity

1. Open the URL in your browser. Verify the domain is exactly antigravity.google — any other origin is suspicious.
2. Download the installer for your operating system.
3. Run the installer and follow the wizard with default options.
4. Open Antigravity and sign in with your Google account when asked. The login is between you and Google; KaKeKiKoKu is not involved.

If Antigravity is new to you. First open a small folder, talk to the agent, and see how it applies changes. This guide covers the KaKeKiKoKu integration, not Antigravity itself.

1. Register KaKeKiKoKu as an MCP server

Antigravity 2.0 manages reusable MCP servers from Settings > Customizations > Installed MCP Servers. Google now treats these customizations as global and reusable across Projects. The IDE and CLI additionally support a workspace-local file.

Option A: Antigravity 2.0 settings (recommended)

1. Click Settings at the bottom-left of Antigravity 2.0.
2. Select Customizations.
3. Open Installed MCP Servers.
4. If the UI offers a custom command entry, add a local STDIO server named wuniq with the command for your OS.
5. If KaKeKiKoKu is not listed in the MCP Store and the build exposes only store entries, use the global configuration file in Option B.
6. Enable KaKeKiKoKu and use the Refresh control after saving.

Option B: Global configuration file

The current Antigravity product family uses a dedicated sparse MCP profile under ~/.gemini/config/. This replaces the older ~/.gemini/antigravity/ and ~/.gemini/antigravity-cli/ MCP paths.

%USERPROFILE%\.gemini\config\mcp_config.json

~/.gemini/config/mcp_config.json

Option C: Workspace configuration for Antigravity IDE or CLI

If you specifically use Antigravity IDE or Antigravity CLI and want KaKeKiKoKu only in one repository, create:

<your-project-root>/.agents/mcp_config.json

This scope is preserved for the IDE/CLI. Antigravity 2.0's newer Project model manages reusable MCPs globally, so do not assume a workspace file is the primary path for the standalone app.

Add the KaKeKiKoKu configuration

Use the JSON block below in the selected mcp_config.json. If it already contains other servers, keep them and add wuniq as a sibling inside mcpServers.

{
  "mcpServers": {
    "wuniq": {
      "command": "wuniq-mcp.exe"
    }
  }
}

{
  "mcpServers": {
    "wuniq": {
      "command": "/snap/bin/wuniq.wuniq-mcp"
    }
  }
}

Windows path note. Use the alias wuniq-mcp.exe. Do not point Antigravity at an absolute path under C:\Program Files\WindowsApps\...; Windows protects that folder and external MCP clients can hit Permission denied or EPERM.

Return to Settings > Customizations > Installed MCP Servers, click Refresh, and confirm KaKeKiKoKu is enabled. For an IDE/CLI workspace file, start a new conversation or use the CLI's /mcp manager to reload the configuration.

For Google's current UI, paths, transports, and schema, see the official Antigravity MCP documentation.

2. Startup instructions (the second piece of the integration)

This is the second of the two pieces every integration needs. Antigravity's current persistent-instruction surface is an Always On rule. Workspace rules live under .agents/rules/; global rules live in ~/.gemini/GEMINI.md.

1. Open Customizations > Rules.
2. Select + Workspace so the rule stays with the project, and set its activation to Always On.
3. Name the rule wuniq and add:

   # KaKeKiKoKu Studio (Knowledge Engine)
   
   At the start of every session, run `open list` using the KaKeKiKoKu MCP tool. If it returns projects, `open` each one. If the list is empty, proceed normally — the user may open projects later from the KaKeKiKoKu UI. Never assume the working directory is a KaKeKiKoKu project; the working directory may be a container folder holding multiple projects. Only open paths that `open list` explicitly returns.
   
   Before working on any code file, `read` its KaKeKiKoKu sidecar for context. After changing code, run `sync`.

4. Save and start a new Antigravity conversation.

Manual file equivalent. Create .agents/rules/wuniq.md in the workspace or Git root. Antigravity still supports the older .agent/rules spelling, but new configuration should use .agents/rules.

Existing AGENTS.md or GEMINI.md. Antigravity continues to recognize those project context files. Keep them; do not delete or replace richer existing guidance. A dedicated Always On KaKeKiKoKu rule is recommended because its activation is explicit and it does not overwrite the rest of your project instructions.

3. Apply the changes

MCP configuration and startup instructions are not applied the same way. Reload the surface you actually changed:

• Antigravity 2.0 global MCP configuration — Return to Settings > Customizations > Installed MCP Servers, click Refresh, and confirm KaKeKiKoKu is enabled.
• IDE/CLI workspace MCP configuration (.agents/mcp_config.json) — Start a new conversation in that workspace. Antigravity CLI users can also open the /mcp manager.
• Workspace rule (.agents/rules/wuniq.md) — Confirm that its activation is Always On, then start a new conversation. Persistent instructions are assembled when the conversation begins.
• Existing AGENTS.md or GEMINI.md — Start a new conversation after editing either file.

If something still looks wrong after refreshing or restarting the conversation, close Antigravity completely, reopen it, and start a fresh conversation.

4. Start a conversation and verify

1. Open the Project that contains your real KaKeKiKoKu-managed folder and start a new conversation. For the first test, prefer Local mode so paths match directly.
2. If your startup instructions are loaded, the selected agent model should call KaKeKiKoKu automatically. If not, ask:

   Run open list with the KaKeKiKoKu tool.

3. If everything is connected correctly, the agent will list the projects KaKeKiKoKu knows about.
4. Ask the agent to open the project you want, or let the startup instruction open every returned project.
5. In the KaKeKiKoKu interface, the AI-connected indicator should turn green when Antigravity starts using the tool.

Quick test

Inside Antigravity, ask:

Read the project index with KaKeKiKoKu.

The agent should use the wuniq MCP tool. If it answers from general memory, ask explicitly to use KaKeKiKoKu and re-check that the workspace rule is enabled as Always On.

5. Working in Precise mode

In Precise mode, KaKeKiKoKu cannot push messages to the AI. This changes the daily flow:

• Starting a session. If you created the startup instructions, the agent should open KaKeKiKoKu projects automatically. If it does not, ask it to run open list with the KaKeKiKoKu tool.
• Sync. When you edit code, KaKeKiKoKu detects drift in its panel. Ask the agent to run sync when you want it to reconcile code and context.
• "Talk to AI" buttons. In Precise mode, these copy a prompt to the clipboard. Paste it into Antigravity when you want the agent to act on it.
• Drift alerts. They appear in KaKeKiKoKu's UI, not as push notifications in Antigravity.

Recommended KaKeKiKoKu configuration. Go to KaKeKiKoKu > Settings > Application > AI Sync and choose Precise mode.

6. Plan and model

KaKeKiKoKu works through the model Antigravity orchestrates; it does not use the Google API directly. As of July 2026, Google documents Gemini 3.5 Flash and Gemini 3.1 Pro across Antigravity plans, with models such as Claude Sonnet 4.6, Claude Opus 4.6, and GPT-OSS-120B available on Ultra depending on the plan and current rollout.

Choose the model from the selector below the prompt. Antigravity keeps that choice for subsequent conversations until you change it. Model availability, quotas, tool support, and context limits are controlled by Google and may differ by plan.

KaKeKiKoKu does not require the entire repository to fit into one prompt. It loads context progressively with search and read tools, preserving the existing advantage of smaller, targeted context even when a long-context model is available.

See Google's official Antigravity model documentation for the current model list and plan restrictions.

7. Troubleshooting

KaKeKiKoKu doesn't appear after editing the configuration file

1. Verify you saved and closed the file before starting a conversation or clicking Refresh.
2. If using local configuration, make sure the file is placed at .agents/mcp_config.json (under the .agents directory, not directly in the project root).
3. Verify the JSON is valid (no trailing commas, braces well-closed). If in doubt, paste the content into an online validator.
4. If using global configuration, go to Settings > Customizations > Installed MCP Servers and click Refresh.
5. If it still doesn't appear, close Antigravity completely, reopen it, and start a new conversation.

A configuration file was saved with a BOM

If KaKeKiKoKu never loads and Antigravity's logs show an error like invalid character 'ï' looking for beginning of value, the file was saved with a UTF-8 BOM — a hidden 3-byte marker at the very start of the file. Antigravity's configuration parser is strict and rejects it.

You cannot see a BOM in the editor, and an online JSON validator will not catch it — most validators silently tolerate a BOM. It is added at save time by some tools: classic Notepad's UTF-8 option, or PowerShell's Set-Content -Encoding UTF8.

Fix: re-save the configuration file (either local or global) as UTF-8 without BOM. Editors like VS Code, Notepad++ or Antigravity's own editor show the current encoding in the status bar and let you switch it to UTF-8 (without BOM). Then reload by starting a new conversation or clicking Refresh.

KaKeKiKoKu appears but is disabled

In Settings > Customizations > Installed MCP Servers, click the toggle next to KaKeKiKoKu to switch it to Enabled. Without this, Antigravity will not call the server.

The agent doesn't use the KaKeKiKoKu tool

1. Make sure the conversation starts with KaKeKiKoKu in Enabled state.
2. Confirm that .agents/rules/wuniq.md exists in the correct workspace and its activation is Always On.
3. Ask explicitly:

   Use the wuniq tool to read context before answering.

4. If the model systematically ignores the tool, confirm the selected model and current plan support MCP tool calls.

"Permission denied", "Access denied" or "EPERM" error on Windows

Usually happens if you configured an absolute path inside C:\Program Files\WindowsApps\.... That folder is protected by Windows. Antigravity can see the file, but cannot execute it correctly as an MCP server.

Fix: edit the configuration file and leave the command as:

wuniq-mcp.exe

Without absolute path. Reload or click Refresh.

where.exe wuniq-mcp.exe returns nothing

Windows can't find the KaKeKiKoKu MCP alias. Check:

1. That KaKeKiKoKu is installed.
2. That you can open KaKeKiKoKu from the Start menu.
3. That your PATH includes %LOCALAPPDATA%\Microsoft\WindowsApps.

If you just installed KaKeKiKoKu, close and reopen PowerShell.

Linux command is not found

Check that the KaKeKiKoKu Snap is installed and that this command exists:

/snap/bin/wuniq.wuniq-mcp

Confirm you installed KaKeKiKoKu in the same Linux user account that runs Antigravity.

KaKeKiKoKu cannot see projects outside your home folder on Linux

The KaKeKiKoKu Snap is sandboxed. Projects under your home folder work by default. If your projects live in /mnt/, /media/, a USB drive, or a VM shared folder such as /mnt/hgfs/, grant the needed Snap permission:

sudo snap connect wuniq:removable-media

Then reload the KaKeKiKoKu web UI and open the project again.

Antigravity sees KaKeKiKoKu, but KaKeKiKoKu doesn't show as connected

1. Make sure the Antigravity conversation is active.
2. Ask explicitly:

   Run open list with the KaKeKiKoKu tool.

3. Look at the KaKeKiKoKu interface. The AI indicator should switch to connected when Antigravity uses the tool.

Still stuck?

Email support@kakekikoku.com with your operating system, Antigravity version, and the contents of your mcp_config.json. KaKeKiKoKu can also generate a diagnostic report (Support function in the app) that captures the infrastructure state — attach it to the email.