Up to $250 in free Claude Code credits: how to claim them, and 3 agents to run in the cloud
Anthropic is giving Pro subscribers $100 and Max subscribers $250 to try Claude Code cloud sessions, to claim before October 7. The five-minute process, then three ready-to-run agents that work on your site while your laptop is closed.
September 26, 2026 · 6 min read
Anthropic took Claude Code cloud sessions out of preview on September 23, 2026. A cloud session is Claude Code running on a machine hosted by Anthropic instead of your computer: you give it a task, you close your laptop, and the work keeps going.
For the launch, Pro subscribers get $100 in credit and Max subscribers get $250, usable only in these cloud sessions. A credit you don't claim before October 7 is gone.
This article first gives you the exact steps to claim it, then three ready-to-run agents to spend it on what grows a business: search rankings, conversion, and visibility in AI answer engines.
The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.
Join the Lab →Claim your credits
Open claude.ai/code with the Claude account on your subscription. If you prefer the terminal, the /claim-credit command in Claude Code does the same thing.
Step by step
/claim-credit in Claude Code.From your terminal, you start a cloud session with claude --cloud followed by the task, from your repository's folder. The virtual machine clones the branch pushed to GitHub, not your local files: push your latest commits before you launch.
claude --cloud "Describe the task you want the agent to run"
Three agents to run in the cloud
Each agent below is a cloud session: one prompt, one repository, and a pull request to review at the end. Nothing goes live without your approval, you stay in control of what gets merged. And since every claude --cloud creates its own session, you can launch all three in parallel and come back when they're done.
The technical SEO agent
It goes through your site page by page and fixes what stops Google from understanding and ranking your pages: titles, descriptions, images without alt text, internal links, orphan pages.
You are a technical SEO expert. Audit every page in this repository and fix directly in the code:
1. Every page has a unique title tag under 60 characters and a unique meta description under 155 characters, written to earn the click.
2. Every image has alt text describing what it shows.
3. Every page has exactly one H1, and the H2 and H3 hierarchy is logical.
4. Add relevant internal links between pages covering related topics, and flag the pages nothing links to.
5. Check that the sitemap and robots.txt exist and cover every public page.
Do not change the design or the editorial content. Create a branch called technical-seo, then open a pull request listing every fix, page by page.
The landing page variants agent
It takes your main sales page and builds two variants to test, each on a different angle. You get what you need for an A/B test without waiting for a designer.
You are a conversion expert. This site's main sales page is [PAGE PATH].
Analyze its promise, its structure and its call to action, then create two variants in new files, without touching the original page:
- Variant A: same structure, new headline and subheadline focused on the concrete result the customer gets.
- Variant B: reorganized structure that puts the proof (testimonials, numbers, client logos) before the offer.
Keep the existing design, the same components and the same call to action. Do not invent any testimonial or number: reuse only those already on the site.
Create a branch called landing-variants and open a pull request explaining the hypothesis each variant tests.
The AI visibility agent
It makes your site readable by AI answer engines: structured data, frequently asked questions, and an llms.txt file that summarizes your business for the models.
You are an expert in optimizing for AI answer engines. On this repository:
1. Add schema.org structured data in JSON-LD suited to each page type: Organization on the homepage, Service or Product on offer pages, Article on articles, FAQPage wherever an FAQ exists.
2. On the three most important service pages, add a frequently asked questions section of 4 to 6 questions, written only from information already on the site.
3. Create an llms.txt file at the root of the public site that describes the business, the offers and the key pages in a few lines, with their links.
Do not invent any information. Create a branch called ai-visibility and open a pull request listing every addition.
Going further
Launch all three agents the same evening, one claude --cloud per task. The next morning, three pull requests are waiting on GitHub: you review the diffs from claude.ai/code, ask for adjustments in the same session, then merge what works for you.
What matters next is measurement. Note the merge date of each pull request, and in four weeks look at how impressions moved in Google Search Console, how your sales page conversion rate changed, and how many visits arrive from AI assistants. The credit is free, your review time is not: keep the agents that move one of those three numbers.
Want to go further?
In the Lab, I share my Claude agent and sub-agent setups, and how to run them in parallel without breaking things.
A dedicated session or program, tailored to your tools and use cases.
And day-to-day, I post one reel a day on Instagram: @quentin_iamarketing