Support · Pallas

Installation

Use macOS with Node.js 22 or later, Codex or Claude Code, and internet access during installation. The public npm installer can reuse a supported Python installation or prepare one for the project. You do not need an npm account or a separate wheel file.

Run this in a terminal:

npx pallas-ads install

Choose your agent and a new, empty project directory when prompted. The installer prepares the local runtime, project connection, Skills, and sample data. It does not authorize an advertising account. Keep the generated project and its adjacent runtime directories together; do not move them separately. For options, diagnosis, and updates, see the npm installation guide. The native plugin guide describes the other installation path; use one path per project.

Connect your agent

Open the project directory selected during installation in the agent you chose. Confirm project trust and requested local tool permissions, then start a new task. The installer has already prepared the project connection; media sign-in is a separate step. If the Pallas tools are missing, replace the example directory with your actual project path and run this in a terminal:

npx pallas-ads doctor --directory /absolute/path/to/project

Follow the diagnosis before retrying the connection.

Codex

Open the installed project in Codex and start a new task. Confirm that the Pallas tools and Skills load. The npm installer creates the project-local MCP entry; it does not give every Codex project access to Pallas.

Claude Code

Open the installed project in Claude Code. Confirm that the Pallas tools and pallas-workflow and pallas-analysis Skills are available before asking for analysis.

Try an example without an advertising account

Ask your agent to preview samples/meta_campaign_daily.csv in the installed project. Review the account, dates, field mapping, currency, and missing data before confirming an import and report. This sample is synthetic, not a real account result.

Meet /pallas: the entrypoint for analysis, dashboards, help and status.

Authorization

Google Ads: publisher-configured releases include the Desktop application identity, so you complete browser login without importing a configuration file. Older public core builds omit this identity and need a corrected release from the publisher. Google application verification, API project access and your account permissions still apply. Broader real-account analysis validation remains pending.

Meta Ads: publisher-configured releases use Pallas's browser login on both hosts, with a Pallas HTTPS page returning the authorization result to your computer. No local certificate or /mcp command is required. Deployment, platform approval and fresh external-user acceptance must be completed before this route is generally available. Its data adapter remains pending; login alone does not enable reports. Existing host-managed connections remain separate. Review the consent screen and the authorization guide.

TikTok Ads: use the documented official MCP browser authorization path. Account and platform permissions still apply. An available report path does not mean every live metric has been reconciled.

Choose the connection route for your platform and agent before signing in.

To analyze a CSV or XLSX export, you can skip media authorization. The current import flow is for one platform, one account and one currency at campaign/day granularity; preview and confirm its interpretation before importing.

Questions

Which agents are supported?

The documented integrations are Codex and Claude Code. Their project and media setup paths differ. The logos do not imply integration with the ChatGPT chat website.

Does Pallas run a model or optimize my ads automatically?

No. Your agent handles reasoning and interaction. Pallas supplies local tools and reports and does not modify advertisements.

Authorization failed. What should I do?

Check your agent, connection setup, application eligibility, and media-account permissions. Read the reported error and any cleanup warning. Retrying cannot remove platform access restrictions. Send a redacted error description to support if needed; do not send credentials.

Can I use an existing project?

The npm installer targets a new or empty dedicated directory. It does not merge into an existing coding project. Follow the plugin guide if you are moving an npm project to the native plugin.

How do I update an npm installation?

Close active Pallas tasks and back up the project. Replace the example directory with your actual project path, then run:

npx pallas-ads@latest update \
  --directory /absolute/path/to/project

Updates keep project data and configuration; review the npm installation guide before switching installation paths.

How do I revoke access or remove data?

Follow Data deletion. Revoking platform access, removing local or host credentials, and deleting reports are separate actions.

Contact

For help, email the developer. Include your OS, agent, installation path, platform, and a short description. Remove tokens, passwords, account identifiers, and sensitive advertising data from examples.