Skip to main content
When the Co-founder recommends something concrete — new metadata, a review reply, an issue for your team — it doesn’t just describe it. It prepares the exact change as an action and puts it in your queue. You decide.

​
Review the queue

Open App Co-founder → Actions. Each card shows the change, why the Co-founder wants it, and the data behind it. You can approve or reject one card at a time, or all pending cards at once. You can also decide from where the action reaches you:
  • Email: each briefing email carries one-click approve and reject links for up to five decisions.
  • Slack and Telegram: approval buttons on the message.
  • Chat: Approve and Skip under the Co-founder’s reply.
A pending action the Co-founder stops re-proposing for 14 days is retired automatically, so the queue stays current. A rejected idea comes back only when new evidence changes the case.
App Co-founder → Decisions keeps the full history: every action, what you decided, and what happened next when it could be measured.

​
What it can propose

​
Read and write modes

Settings → Automation → Agent mode decides whether the Co-founder may change things outside Appeeky at all.

​
Autopilot level

Autopilot level sets how much runs without asking. Write access still needs write mode.

​
Auto-approve

Pick action types that skip your approval, such as Slack summaries or review replies. Auto-approve only applies in write mode; in read mode everything waits for you.
Some actions always need your approval, at any autopilot level and even when auto-approve is set: ads changes, monetization changes, win-back campaigns and UGC clips. Coding agent tasks never auto-approve by autopilot level; only an explicit auto-approve setting lets them through.

​
Policy rules

Settings → Automation → Policy rules give you a hard override per action type: For rules the Co-founder must follow in its recommendations — “never suggest removing the free tier” — use the hard rules in your business profile.