What the agent will never do

Overview

The agent's limits are structural rather than settings. They are the reason it is safe to leave running, and none of them can be turned off.

Publishing

The recurring agent never publishes store content. Not on a schedule, not after a successful run, not because it is confident.

Accepting a metadata proposal updates a Spek draft. Publishing that draft, submitting an event or product page, toggling visibility, or starting a real store test are each separate actions that a person must explicitly request, governed by what the store currently allows.

Agent chat can carry out a direct interactive publish command when the user's role and the app's App Store Connect prerequisites allow it. It writes the requested or pending locale drafts and submits the eligible version to App Review. That authority exists only for the verified message and cannot be borrowed by a scheduled run, an attachment, quoted text, an earlier message or the model itself.

Store access

The agent reaches App Store Connect only through its official token API, using the credential your workspace supplied. There is no Apple ID login, no stored session, no cookies and no headless browser driving a console on your behalf.

This is a safety boundary rather than an implementation detail. It is explained in how store connections work.

Data

Every keyword the agent proposes came from a real store response. Nothing in the discovery path may emit a term that was not seen in a store's own search or autocomplete results.

The same applies to numbers. If a market's research has not resolved yet, the agent waits rather than drafting against partial data, and it will tell you a value is unavailable rather than producing a plausible one.

Customer-facing answers describe Spek research and Spek estimates. They do not name outside ASO tools or contrast a Spek number against another vendor.

Scope

Some things simply are not connected, so the agent cannot reason about them however you ask it to.

• Store impressions, product page views and downloads.
• Conversion rate, and anything derived from it.
• Apple Search Ads, including its popularity data.
• The results of store-run product page tests. The agent can draft one; it cannot read back how it performed.
• Revenue, retention and anything from inside your app.

What it does measure is keyword rank and the search visibility derived from it. See what Spek measures.

Beyond that, the agent works only inside the scopes you granted, on the markets you chose, for the app you set it up on. A capability that is not in its scopes does not exist as far as a run is concerned.

Paid research and screenshot generation start only from your direct, verified command. Stop cancels work that is still queued. If the paid provider call has already started, Spek does not send it again; it waits for the worker's real result or shows that reconciliation is needed.

Common questions