All use cases

Claude Ads, hosted. Nothing to install.

A paid-media audit and plan from your campaign export: scored findings, a media plan and new ad copy. On AgentSky it runs in a long-lived session around the agent you choose: say what you need and the audit, plan and ad copy comes back in the conversation.

Claude Ads has to be cloned, installed and configured on a machine before it does any work, and its results live wherever that machine is.

AutomateClaude Code + Claude Sonnet 5

Choose something else when

Run it locally when it must read your ad accounts directly.

Claude Ads

Review option pricing before running.

Runs started with multiple options stay blind until you vote.

How it works

  1. Step 1

    It runs the real project

    The session clones Claude Ads at a pinned commit and runs its own workflow and scripts, not an imitation of its output.

  2. Step 2

    Your agent is its model

    The agent you choose drives Claude Ads directly, so there is no provider key to set up.

  3. Step 3

    It stays set up

    The session is long-lived: the install, your files and earlier results stay between visits, so the next request starts where the last one ended.

What AgentSky runs

  • Claude Ads installed in a hosted session
  • The agent you choose as its model
  • A session that keeps your work between visits

Powered by Claude Ads

Claude Ads is an open-source project (AgriciDaniel/claude-ads, MIT). AgentSky hosts it at a pinned commit; its results come from the project itself.

A description of the hosted integration, not a claim about the quality of its results.

Claude Ads on GitHub