Get Started

Agenda Panda is an agent-first social scheduling CLI for teams that want content review to feel like code review. The happy path is simple: install ap, authenticate, connect a platform, generate or edit a calendar.json, dry-run the sync, and open the dashboard before applying.

1. Start with one agent prompt

If you use Claude Code, Cursor, Codex, or another coding agent, hand it one onboarding prompt instead of narrating the whole workflow step by step:

claude "Fetch https://agendapanda.com/SKILL.md to learn how to use Agenda Panda. Then connect my X and LinkedIn accounts, run ap context --json, build a calendar.json for next week's launch posts, preview it with ap calendar sync --file calendar.json --dry-run, and open ap dashboard for my review. Do not create the calendar one post at a time."

2. Or install it yourself

curl -fsSL https://agendapanda.com/install.sh | bash && ap init

ap init walks through login, workspace selection, first connection setup, and an optional first post.

3. Authenticate

For humans and agents in interactive shells, Agenda Panda uses a device-auth flow:

ap auth login

The CLI prints a code and a browser link. Open the exact URL, approve the session, and the terminal resumes automatically.

For CI/CD or headless automation, use an API key instead:

export AP_API_KEY=ap_your_key_here
ap auth status

4. Connect one platform

ap connections add x
ap connections add linkedin

If you are in a remote or agent shell, print the auth URL instead of trying to open a browser:

ap connections add x --no-open --json

Agenda Panda currently supports X, LinkedIn, Facebook Pages, Instagram, Threads, Bluesky, and TikTok.

5. Review a calendar before you publish

The default product workflow is: gather brand context, generate or edit calendar.json, dry-run the sync, review visually, then apply.

ap context --json > context.json
# Ask your model or agent to create calendar.json
ap calendar sync --file calendar.json --dry-run
ap dashboard
ap calendar sync --file calendar.json

Multi-agent safe default

In CI or multi-agent workflows, prefer explicit --project and --connection flags over mutating shared defaults with ap projects use or ap connections use.

6. Publish one post when you do not need a calendar

ap post "Hello from Agenda Panda" --connection x
ap post "Launch visual" --media-id abc12345 --schedule 2026-05-01T14:00:00Z

If you do not have a connection yet, ap post can prompt you to connect one inline.

Where to go next

• Quick Start for a fuller walkthrough
• CLI Overview for install, flags, and command map
• AI Workflows for agent-first calendar and media workflows
• Calendar as Code for JSON file structure and review flow