SFEED.DEV
Docs FAQ Privacy Terms

Cookbook

These are short recipes you can copy, run, and adapt. Each one keeps the moving parts small so you can see what sfeed is doing.

Recommended local setup

If you want to use sfeed with an agent, start with Filesystem setup. That guide shows how to keep your posts, media, and rules on disk and let the agent use sfeed as the publishing layer.

Before you start

sfeed auth facebook
sfeed status
sfeed pages

If you have one connected Page, sfeed post uses it automatically. If you have more than one, pass --page.

Recipe 1: Post text to Facebook

sfeed post "Shipping v0.1.2 today." --to facebook --page "Acme Robotics" --dry-run
sfeed post "Shipping v0.1.2 today." --to facebook --page "Acme Robotics"

Use this for the smallest possible post flow. Start with --dry-run when you want to check the page and platform before publishing.

Recipe 2: Post an image from a local file

sfeed post "Launch image" --to instagram --page "Acme Robotics" --media ./assets/launch-card.jpg

sfeed stages the local file automatically when the target needs a public media URL. That works for Instagram and for scheduled posts.

Recipe 3: Post a video

sfeed post "Release clip" --to facebook --page "Acme Robotics" --media ./assets/release-clip.mp4
sfeed post "Release clip" --to instagram --page "Acme Robotics" --media ./assets/release-clip.mp4

Facebook supports one video per post. Instagram supports one image, one video, or an image-only carousel.

Recipe 4: Schedule a post for later

sfeed billing
sfeed post "Tomorrow at 9am" --to facebook --page "Acme Robotics" --media ./assets/launch-card.jpg --at "2026-04-06T13:00:00Z"
sfeed schedule status
sfeed dashboard
sfeed schedule preview <id>

Hosted scheduling requires a subscription. Scheduled local-file media must be within 90 days, and staged local files must be 100 MB or smaller.

Recipe 5: Check failures and posted jobs

sfeed schedule list --status failed
sfeed schedule list --status posted

Use this to see what failed, what posted successfully, and what still needs attention.

Recipe 6: Pick the right page when more than one is connected

sfeed pages
sfeed post "Post this on the Acme page" --to facebook --page "Acme"

When more than one Page is connected, keep the page choice explicit. That makes agent workflows and manual workflows behave the same way.

Recipe 7: MCP workflow for agents

  1. Start with sfeed mcp
  2. Ask the agent to read your local content folder and rules file first
  3. Call sfeed_status
  4. If more than one Page is connected, call sfeed_pages
  5. Ask the agent to draft the post
  6. Call sfeed_post

Recipe 8: Post from a local content folder

social/
  rules.md
  queue/
    2026-04-10-facebook-launch.md
  media/
    launch-card.jpg

Then tell your agent:

Read ./social/rules.md and ./social/queue/2026-04-10-facebook-launch.md.

Show me the draft first.

If I approve it, use sfeed to schedule the post with ./social/media/launch-card.jpg.

This is the simplest version of the local-files workflow. Your content stays on disk, and sfeed only handles the actual posting and scheduling.

Recipe 9: Route different drafts to different guides

Use these when you want a shorter guide that matches one exact workflow and query.

Recipe 10: Start with a rules file

If your agent is making the right technical calls but the wrong posting decisions, add a small rules file first.

Record these demos

If you want short demo videos, these three flows are enough:

Using sfeed with Codex

Using sfeed with Claude Code

Using sfeed with OpenCode

Back to Docs