What happened
Google Antigravity's November 9, 2026 announcement says people are bringing the product work beyond code: deep research, data analysis, document and presentation drafting, design prototyping, and everyday workflow automation. Google says tens of thousands of its employees outside software engineering use Antigravity each week, including people in sales, finance, legal, product, design, research, marketing, and operations.
Google has therefore introduced two selectable layouts in the Antigravity App: Knowledge Work and Software Engineering. Existing users keep Software Engineering as their default. According to the announcement, both layouts run the exact same Antigravity agent and have access to frontier models, local files, plugins, skills, rules, custom agents, and MCP servers. The company positions the change as a way to make professional knowledge work more approachable without removing the system's underlying capabilities.
The Knowledge Work layout changes the visible workflow. It creates folder-backed projects and standalone No Project conversations without Git worktree prompts, while hiding Git branch pickers and IDE handoff buttons. In a conversation, expandable tool-call groups, inline code diffs, and subagent cards give way to a live progress line that clears when the turn ends. Permission prompts present plain-language summaries rather than developer-oriented detail.
The Overview and Side Panel remain tucked away until a conversation produces output. The main surface removes Review and Terminal, renames the Files tree to Folders, and centers Documents, Artifacts, Links, Uploads, and Background Tasks. Extensions remain visible when UI plugins or MCP Apps are active. Google has also rolled out role-based onboarding for new users: Software Engineering, Knowledge Work, Data & Analytics, Science, and Design selections tailor the starting layout, starter prompts, and recommended plugins.
Users can switch through Settings > General > Interface Layout, with Cmd+, on macOS and Ctrl+, on Windows or Linux. Google says the switch takes effect immediately in open and new conversations and requires no restart. The announcement directs people to download Antigravity to try the layout today, but does not state a separate price, plan, or eligibility rule for it.
What the archive adds
New Runtime's November 6, 2026 note on Antigravity Voice Mode covered a spoken interface for directing an agent while it works. This is a new interface change on that known product story: rather than adding another input modality, Google is reorganizing the main workspace for people whose work is not centered on repositories and code review.
Trend signal
This supports New Runtime's shift on coding agents as general workbenches: vendors will keep positioning coding agents for general knowledge work rather than splitting them into developer-only and consumer products. Google retains one agent, its models, local-file access, plugins, skills, rules, custom agents, and MCP servers; it changes the presentation around them for different roles.
Why now
Google frames the update as a response to observed behavior. Its announcement says sessions increasingly cover research, analysis, writing, design, and workflow automation, while employees outside software engineering use the product weekly. The company describes the layout as an initial response to that pull, not as a completed solution for every role. Software development remains central to Antigravity in Google's framing.
Why it matters
A cross-functional agent rollout can fail on interface friction before model quality becomes the limiting issue. People working in operations, finance, product, or research may not want to navigate Git worktrees, terminal panes, branch pickers, or line-by-line diffs simply to ask for a document, analysis, or automation. An outputs-first surface and plain-language permission summaries may make a shared agent environment easier to adopt without forcing teams onto a separate, lower-capability product.
The important constraint is that simplification is not validation. The layout does not change the need to review consequential outputs, manage access to local files and connected tools, or establish responsibility for decisions. A team should treat this as a workflow experiment: choose a recurring task, define what an acceptable result looks like, compare the two layouts with the people doing the work, and preserve review steps appropriate to the task's risk.
Limits and uncertainty
Google provides no independent measurement of task success, time saved, user preference, or error rates for the two layouts. It does not quantify adoption outside its own workforce, usage of the named features, or whether plain-language permission summaries change approval decisions. The company says the underlying capabilities are unchanged, but it does not publish task-level comparisons for research, analysis, writing, design, or automation. Its internal adoption figure and rationale are company claims rather than independently verified outcomes.
Skill to build now
Run a small interface-fit test before broadening an agent rollout. Give a non-engineering teammate one bounded recurring task, such as preparing a research brief or organizing a project folder, and define the required output, permitted connected tools, and reviewer. Have them perform the task in Knowledge Work and record where they need developer concepts or cannot verify the result. This separates interface friction from agent reliability.
Reader takeaway
Antigravity's Knowledge Work layout changes the product's presentation rather than the agent underneath it. Teams already using Antigravity can switch immediately and evaluate whether documents, artifacts, and simpler approvals make cross-functional work easier, while keeping the same controls over access and review that serious agent workflows require.