Filesystem Setup

If you want to use sfeed with Claude, Codex, OpenCode, or another agent, a simple local filesystem setup makes the whole workflow easier. Your files stay local, the agent reads them, and sfeed handles the actual posting.

Example folder tree

folder
Local Content Folder
One simple setup for agent-driven posting
folder_open social/
description rules.md # posting rules and page choices
folder queue/
article 2026-04-10-facebook-launch.md # draft post
article 2026-04-11-instagram-clip.md # scheduled draft
folder media/
image launch-card.jpg # image asset
movie product-demo.mp4 # video asset
folder archive/
folder 2026-04/ # already posted files
folder prompts/
description weekly-plan.md # reusable planning prompt

What goes where

Example rules file

# Social posting rules

- Use page: Lound - AI Voice Journal
- Prefer Facebook for text-only posts
- Prefer Instagram when a post has an image
- Schedule new posts for 9am Eastern unless the file says otherwise
- Do not post without showing me a draft first
- Move posted files into archive/ after success

Example draft post

---
platforms: facebook,instagram
media:
  - ../media/launch-card.jpg
schedule_at: 2026-04-10T13:00:00Z
---

Shipping today.

The new queue UI and scheduled preview flow are live in sfeed.

How the agent should use it

  1. Read rules.md
  2. Inspect the files in queue/
  3. Choose the right page and platform from the rules and frontmatter
  4. Show you the draft
  5. Use sfeed to post now or schedule it
  6. Move the file to archive/ if your workflow says to do that

Example prompt

Read ./social/rules.md and the files in ./social/queue.

Show me the next post draft first.

If I approve it, use sfeed to schedule it with the media files referenced in the draft.

Why this works well

You keep control of the source material on your own machine. The agent gets clear local context. sfeed stays focused on auth, posting, scheduling, previews, and the queue instead of becoming your content store.

Read next

Back to Docs