Any Useful Skills?
What skills you guys are using right now? Is there like a marketplace to get skills?
What skills you guys are using right now? Is there like a marketplace to get skills?
I just ran Google Antigravity from my phone !!!
No labtop
No Desktop
Only a phone
And Yes got it working using Termux.
#Ai #antigravity #SWE #SoftwareEngineer #Google
I am really not sure if it's just my preference for console apps, but for some reason the web chat interface for Gemini feels like the simple country cousin to AGY CLI using the same models. I tried giving both interfaces the same rubber ducking tasks and the difference was night and day in tone and depth of search results.
Just curious if it's me or if that's something others have noticed.
I asked Gemini Flash 3.8 on Antigravity CLI (running on Termux in Android) whether it can make my local MCP toolset to load eagerly. It started normally by loading the customization skill and reading the included documentation. Then when it found nothing, it went straight to using `ps` and `command -v` to find its own binary, then `strings` to search it for relevant JSON tags. After a few searches, it even ended up taking a look at the code itself, though I think it gleaned nothing from it.
I was accepting those shell commands individually. It was fascinating to see what it was doing, but it also seemed like a pretty unhinged response to just a simple question. At no point did it ask me anything before it spontaneously started to reverse-engineer the binary.
It did discover that there's a JSON key named `eager`, but didn't ultimately discover its correct use, which is not for the server but for the individual tools. It is also mentioned in passing in the Antigravity CLI's change log, but seems otherwise undocumented.
Anyway, after some trials of my own (`mcpServers.<server>.tools.<tool>.eager = true`), I got the tools i wanted to load eagerly. It seems that it also affects the way the results are processed, with longer output from lazily loaded tools ending up in files that need to be read in separately, but in eager mode delivered directly to context, so it actually saves even more cycles than I thought.
Typing /help displays all available slash commands. However, we cannot memorize every single one, and we can always issue instructions in natural language. Still, typing endlessly on a keyboard gets tedious, so commands serve as an efficient shortcut.
Here is a breakdown with examples:
1. /grill-me : Formulates a plan through an interactive interview with Gemini. It helps uncover aspects you might have overlooked—such as tech stacks, specific rules/constraints, and design decisions—tailored to your requirements.
Example) /grill-me I want to add dark mode to our app. How should I approach this?
2. /teamwork-preview : Spawns specialized sub-agents by domain to divide tasks and collaborate toward a solution.
Example) /teamwork-preview Built and ran the app, but clicking the button does nothing. I have no idea where it broke. Find the root cause.
3./plan : Analyzes the structure and architecture without modifying code, then establishes a step-by-step execution plan.
Example) /planI want to refactor the SQLite-based cache into a hybrid architecture with an LRU cache.
4./boost : Leverages multi-sub-agents to troubleshoot various issues and tackle complex tasks.
Example) /boost Clicking the play button triggered a deadlock and crashed the app. Deduce the root cause and provide a solution.
5./learn : Instructs Gemini to memorize your personal preferences and constraints.
Example) /learn Never use libraries A and B under any circumstances.
6./clear : Clears the workspace and initializes a fresh session. Although it wipes prior conversational context, it is essential for achieving higher-quality task results.
Example) /clear
7./goal : Enables the agent to autonomously set sub-goals and execute the initial instructions to completion without interruption.
Example) /goal Identify and fix all issues until the post-build E2E tests pass 100%.
In reality, what matters most is not how thoroughly you memorize these slash commands. Clearly understanding what you want to achieve is what truly counts. While we cannot know everything—as has always been the case—AI can provide substantial assistance.
Try out these slash commands, compare them with writing direct prompts, and leverage them when appropriate. Although I wrote this guide, entering these dedicated modes via slash commands often takes quite a long time, so I personally only use them occasionally.
Please welcome our new mod u/Aromatic-document638 he is a truly token efficient AGY Builder and a true asset for this community. Thanks for all you do for our community and welcome to the team 💪
Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1w4eqy4/new_useage_will_bankrupt_them/
Original post body :
I'm based in aus its currently 1am wendsday so in 10 h I've used 40% of my weekly limit on the $340 plan . I've been on this plan for months and didn't do anything outside of the norm and never hit a weekly limit and rarely hit a 5h limit. Competitors are catching up and not so cheap. I will not continue on this plan if this is how they decide the future is.
I've been building an app and I have not done or changed the way I use it . The only change is the extra usage and it seems they where giving more then 50% or the change has broken something
I was using fable but that's not abnormal and once I hit that limit I move but 40% of my weekly in 10 hours is ridiculous
Original link/media URL : https://i.redd.it/d17mkilnbxmh1.jpeg
This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.
In May 2026, at Google I/O, Google introduced Antigravity CLI as the lightweight terminal surface of its new agent-first development platform. The command is simply agy. It succeeded the earlier Gemini CLI (On June 18, 2026, Gemini CLI stopped serving requests for free, Google AI Pro, and Ultra users, while access remained available to enterprise customers and through supported paid API keys) and shares the same core agent harness as Antigravity 2.0, the Antigravity IDE, and the Antigravity SDK.
The result is a fast, keyboard-driven Terminal User Interface that brings multi-step reasoning, multi-file editing, tool calling, subagents, conversation history, and secure command execution directly into the shell-especially useful for SSH sessions, remote work, and developers who prefer staying inside the terminal.
Antigravity CLI is deliberately not a full GUI. Where Antigravity 2.0 emphasizes visual orchestration and project management, the CLI prioritizes speed, near-zero overhead, and seamless integration with existing terminal workflows, tmux, and remote environments. Both products run on the identical agent engine, share settings and permissions, and allow conversation export so you can move fluidly between surfaces.
This article synthesizes official documentation, the product announcement, GitHub materials, detailed guides, community cheat sheets, and early YouTube walkthroughs and demos to give a complete picture of what is known about the tool and how to use it productively as of August 2026.
Antigravity is Google’s agent-first software development platform. Agents can read codebases, plan changes, edit files (with permission), run terminal commands, search the web, call external tools via MCP servers, and spawn parallel subagents. The CLI is the terminal-native way to invoke, monitor, and steer those agents.
It is a self-contained Go binary, not a Node.js package. This design choice delivers faster startup, lower resource use, and simpler distribution compared with the previous Gemini CLI. Official materials emphasize three strengths: natural-language interaction for editing and orchestration, subagent parallelism for larger tasks, and a highly configurable, keyboard-centric experience that stays out of the way.
Key differentiators from a pure chat interface or traditional IDE plugins include persistent, resumable conversation history scoped to the current workspace, with a local cache mapping workspace paths to conversation IDs while conversation threads are retrieved through the Antigravity backend, artifact review (plans, diffs, and generated files that you explicitly approve), terminal sandboxing for safer command execution, and the ability to run non-interactively for scripting and CI. Models available include Gemini variants (Flash and Pro families with different reasoning effort levels), Claude Sonnet and Opus, and open-weight options such as GPT-OSS 120B, depending on your account tier and configuration.
The philosophical split is clear: use the CLI when you want speed and terminal flow; switch to Antigravity 2.0 when you need rich visual orchestration or simultaneous multi-project management. Settings and the underlying agent intelligence stay synchronized.
Gemini CLI had grown popular as an open-source terminal agent. Google consolidated its consumer developer surfaces under the Antigravity brand, transitioning most Gemini CLI users to Antigravity CLI while retaining Gemini CLI access for certain enterprise and API-key workflows. The transition preserved many workflows while moving to a closed-source Go binary and a unified harness co-optimized with Gemini models.
Migration is deliberately smooth. On first launch the CLI detects legacy Gemini configuration and offers interactive import of extensions, skills, settings, and tokens into the OS keyring. An explicit command agy plugin import gemini converts extensions into the new plugin layout. Workspace rules (GEMINI.md or the preferred AGENTS.md), skills paths, and MCP configurations receive clear migration guidance, with some directory renames (for example, .gemini/skills/ becoming .agents/skills/). Partial parity exists for highly customized themes, but core developer experience constructs carry over.
YouTube first-look videos and full walkthroughs released the same day as the announcement show the TUI in action building simple applications, demonstrating subagents, and highlighting the shared harness. Community reaction focused on the speed of the Go binary, the quality of the terminal interface, and the practical value of parallel subagents.
Installation is deliberately simple and platform-specific.
On macOS or Linux:
curl -fsSL https://antigravity.google/cli/install.sh | bash
The binary lands in ~/.local/bin/agy. Ensure that directory is on your PATH.
On Windows PowerShell:
irm https://antigravity.google/cli/install.ps1 | iex
On Windows CMD the equivalent curl-based script is available. The binary is placed under the user’s AppData Local directory.
Optional flags include --skip-aliases and --skip-path if you prefer to manage shell configuration yourself. After installation, verify with agy --version. Updates are typically handled in-place. Some users report using package managers such as winget on Windows as an alternative.
The installer is the official and recommended path; avoid third-party mirrors.
Authentication uses the operating system’s secure keyring (Keychain on macOS, Secret Service on Linux, Credential Manager on Windows). If a valid token exists, launch is silent. Otherwise the CLI opens a browser for Google Sign-In (or prints a URL for SSH sessions so you can authenticate locally and paste the code back). Enterprise users can connect a Google Cloud project, use Workforce Identity Federation, or Application Default Credentials.
On first launch inside a project directory the TUI guides you through color scheme selection (Solarized, Dark, Light, or terminal defaults), rendering mode (Alt-Screen full-screen versus Inline), and workspace trust confirmation. Once you trust the directory the agent indexes the files. You can later change these preferences via /config or by editing ~/.gemini/antigravity-cli/settings.json.
Logout is available with /logout. For remote SSH the flow is intentionally designed so the sensitive browser step happens on your local machine.
Navigate to any project directory and type:
agy
You are now inside the TUI. The prompt box sits at the bottom. Type natural-language instructions and press Enter. The agent reasons, may search the codebase, propose a plan, generate or edit files, and request permission for terminal commands.
A classic first tutorial exercise is:
Write a simple python script to fetch web page text
The agent creates a file (typically main.py). Press Ctrl+R to open the Artifact Review screen, navigate with arrow keys, inspect the content and diff, then press y to approve. You can then instruct the agent to run the script and stream the output. Exit with Ctrl+D or /exit.
Useful immediate shortcuts include:
@ to trigger path auto-completion! at the start of a prompt to run a shell command directly? or /help for the command listNon-interactive use is available for scripts and automation:
agy -p "Explain the architecture of this codebase"
Additional flags support model selection, output format (text, json, stream-json), mode overrides, and conversation resumption.
Three primary modes control how aggressively the agent acts:
Cycle modes mid-session with Shift+Tab. Launch with a specific mode via agy --mode=accept-edits or agy --mode=plan. The setting can also be persisted in the configuration file. Note that shell-command permissions remain governed separately by the permission system even when file edits are auto-approved.
Typing / opens a typeahead menu of commands. The surface is rich and grows with releases. Core categories include:
Conversation management: /resume (or /switch), /rewind (or /undo), /fork (or /branch), /clear, /rename, /exit.
Configuration: /config (or /settings), /permissions, /model, /keybindings, /statusline.
Monitoring and tools: /agents, /tasks, /skills, /mcp, /hooks, /diff, /codesearch (aliases /cs or /search).
Utilities: /btw for a side question that does not interrupt the main thread, /open, /usage, /logout.Other built-ins include /context, /copy, /credits, /fast, /feedback, and /planning. Additional slash commands may appear when plugins or Markdown-defined skills are installed.
Many commands have aliases. Custom keybindings live in ~/.gemini/antigravity-cli/keybindings.json and can be edited interactively. Default bindings cover navigation, confirmation (y/n), editor integration (Ctrl+G), and suspension (Ctrl+Z).
Subagents. The main agent can spawn concurrent background agents for research, testing, or parallel file generation. Monitor them with /agents. Approvals can be handled in the detail view or via the fast-path shortcut Ctrl+K. This is one of the features most frequently praised in early demos for accelerating multi-part work.
Plugins, skills, hooks, and MCP. Plugins are self-contained bundles of skills, agents, rules, MCP servers, and hooks. They install under ~/.gemini/antigravity-cli/plugins/. Skills are markdown-defined reusable workflows. Hooks intercept events. MCP servers extend the tool surface; configuration lives in dedicated JSON files (global or workspace). The /mcp, /skills, and /hooks commands provide management interfaces.
Terminal sandbox. Optional lightweight isolation (nsjail on Linux, sandbox-exec on macOS, AppContainer on Windows) restricts potentially dangerous commands. It is configurable and appears in confirmation prompts so you can choose to run inside or outside the sandbox on a per-command basis.
Artifacts and review. Generated plans, diffs, and files appear as reviewable artifacts. Transparency is a core design principle: you see what the agent intends before it writes to disk.
Conversation persistence. Sessions are saved. Closing the CLI prints a resume command; /resume lists prior conversations. You can also export a conversation into Antigravity 2.0 for continued visual work.
Customization. Beyond themes and keybindings, settings.json supports fine-grained permission allow/deny lists, status-line scripting, verbosity levels, and more. Project-level rules can live in AGENTS.md or skill directories.
Start inside a trusted Git repository so you can easily review and roll back changes. Begin complex tasks in plan mode. Use /goal once you trust the direction. Dispatch independent work to subagents. Keep an eye on context and usage with the relevant slash commands. Prefer stronger models for architectural or multi-file reasoning and lighter models for quick questions.
For Flutter and Dart projects the official documentation notes integration with the Dart/Flutter MCP server, making the CLI particularly convenient for mobile and multi-platform work.
Common patterns from early users and tutorials include: summarizing an unfamiliar codebase, implementing a feature with a prior plan, refactoring while verifying against project conventions stored in AGENTS.md, generating tests in parallel, and using non-interactive mode inside CI scripts or commit-message helpers.
Safety habits matter. The free tier has tighter request limits than earlier Gemini CLI offerings. Always review diffs for sensitive projects. Use the sandbox when experimenting. Avoid feeding proprietary secrets into prompts.
The binary is closed-source. Free-tier quotas are more constrained than the previous open-source tool’s generous daily limits. Model availability and performance depend on your Google account and any paid tiers. As with any agentic system, results are non-deterministic; verification loops remain essential. Remote authentication works well but requires the local browser step. Some highly experimental visual customizations from Gemini CLI do not transfer perfectly.
Community feedback on YouTube and blogs notes the speed advantage of the Go implementation, the quality of the TUI, and the practical power of subagents, while also pointing out the quota shift and the need to re-learn a few command names.
Because the CLI and Antigravity 2.0 share the agent harness, improvements to reasoning, tool use, and model integration flow to both surfaces. Google has signaled continued investment in the terminal surface for developers who live in the shell. Releases through the summer of 2026 added Markdown-defined custom agents, progressive streaming for code search, better enterprise sign-in options, structured output formats for headless use, and numerous polish fixes.
Antigravity CLI is not a replacement for every IDE workflow, but for terminal-centric developers, remote sessions, rapid iteration, and agent orchestration it is a significant step forward. Install it, trust a small project directory, run the official tutorial exercise, experiment with modes and subagents, and the tool quickly becomes part of the daily flow.
The combination of a lightweight TUI, a shared high-quality agent core, transparent review, and extensibility through plugins and MCP makes it one of the most practical terminal AI coding experiences available in 2026.
Official documentation and product pages form the primary authoritative base:
Additional practical guides and references:
Selected YouTube resources (official and early independent coverage):
All information above is drawn from these public sources current as of early August 2026. Features continue to evolve; always consult the official docs for the precise behavior of the version you have installed.
The idea: Agents keep the conversation history as part of their input while they reason. SKILL.state proposes to replace that with a structured representation of the current state, and the latest observation.
While the agent reasons through the problem, it writes information it deems useful for future steps into the state. Then it discards the conversation history. So the input size remains roughly the same as the session goes.
They ran a 100-step benchmark with Gemini-3-Flash:
Caveat: This works best if the agent can understand what it will need in the future steps, otherwise that information will not be written, so it'll have to retrieve it again.
Link to the paper: https://arxiv.org/abs/2608.26263
Skills.google >>> dropped yesterday...
>This is taken from the following tweet: https://x.com/googleaidevs/status/2085468449145544780
We’ve put together this cheat sheet of essential slash commands to help you navigate, customize, and execute tasks faster than ever in Google @Antigravity. Whether you're setting up background tasks, tweaking your workspace utilities, or diving into deep research with subagents, these commands will help improve your daily workflow.
🔖 Bookmark this list to save time later.
Get started with Antigravity: https://antigravity.google/
From one of our Mods the one and only u/soundDR
Description from the video:
In this walkthrough, we use Antigravity 2.0 to build two complete custom automations across the Chrome and local OS.
Prompt: Act as an expert Chrome Extension developer and build a Manifest V3 extension that automatically organizes unpinned tabs into native Tab Groups based on their last-accessed time. The time buckets must be exactly: Today, Yesterday, This Week, Last Week, This Month, Last 90 Days, and Archived, calculated strictly using the user's local timezone. When a tab becomes active, its timestamp should update via TTL logic and it should immediately move to the 'Today' bucket. This organization logic must be isolated per window (no cross-window tab moving) and must maintain a stable, fixed left-to-right visual sorting of the tab groups. Persist all tab timestamps using 'chrome.storage.local' to survive browser restarts and Service Worker suspension. Ensure you ignore pinned tabs entirely, and heavily debounce the 'chrome.tabs.onActivated' and 'onUpdated' listeners to prevent Ul flickering and Chrome API rate limits. Please output the complete 'manifest.json' and the 'background.js' service worker code.
Subscribe to Google Antigravity → / @googleantigravity
Google Antigravity is an agentic development platform, evolving the IDE into the agent-first era. Antigravity enables developers to operate at a higher, task-oriented level by managing agents across workspaces, while retaining a familiar AI IDE experience at its core. Agents operate across the editor, terminal, and browser, enabling them to autonomously plan and execute complex, end-to-end tasks elevating all aspects of software development.
To learn more: Website: https://antigravity.go... X: https://x.com/antigravity LinkedIn: / google-antigravity
Trying to figure out which workflow is lighter on background usage between the two Antigravity setups:
For those who have tested both for similar coding tasks:
All the web on one topic in the last 30 days