← Saved-Post EnginePROTEUSX / LABS

OPEN STARTER KIT · V1

Build your saved-post execution loop

Everything you need to collect compliant saved-link inputs, deduplicate them, extract durable lessons, and route the useful ideas into action.

Download the complete starter kit

Before you start

Python

Python 3.9+ and a model-capable command you configure. The core pipeline has no third-party Python dependencies.

X API

Automatic X bookmarks use the official X API OAuth2 bookmarks endpoint with bookmark.read, tweet.read, and users.read scopes. X access and pricing can change; verify your developer tier before setup.

Local by default

Inputs, state, and Markdown output stay in directories you choose. The optional Notion adapter is off unless you provide its documented variables.

Four moves from save to action

1

Configure

Copy .env.example, choose a local state directory, and add only the connectors you use.

2

Collect

Use the official X API, paste/share URLs, or backfill from your Instagram Download Your Information archive.

3

Run

Process once from the command line or install the twice-daily macOS launchd schedule.

4

Act

Review Markdown output by implement, watch, already-adopted, and ignore—each with a concrete next action.

COMPLIANT INPUTS

Three ways in. One inbox.

AUTOMATIC

Official X bookmarks

OAuth2 user-context requests to /2/users/:id/bookmarks. No cookies, session extraction, or private endpoints.

RECOMMENDED

URL / share sheet

Send Instagram, TikTok, LinkedIn, X, or any web URL to the newline-delimited inbox from iOS, macOS, or the one-shot CLI.

HISTORY BACKFILL

Instagram export

Import the JSON, HTML, or ZIP from your user-requested Meta/Instagram Download Your Information archive. Collection names and timestamps are preserved when present.

Instagram: the honest constraint

Meta’s official API does not expose a Saved collection API. Going forward, use share sheet URL intake. Importing your own Download Your Information archive is the compliant history path. Exact native-Save auto-sync would require a separate local-only experimental connector and explicit acceptance of account risk; it is not included or recommended here.

Operations included in the kit

Quick start

unzip saved-post-execution-engine.zip
cd saved-post-execution-engine
cp .env.example .env
chmod 600 .env
python3 -m unittest discover -s tests -v
python3 -m saved_post_engine.cli ingest-url https://example.com/useful-idea
python3 -m saved_post_engine.cli run

Keep the chmod 600 .env step so connector credentials stay private, then open ~/.saved-post-execution-engine/output/digest.md. See README.md for X OAuth, Instagram export, Notion, launchd, troubleshooting, and uninstall instructions.

Want this adapted to a real workflow?

Templates teach the pattern.
ProteusX builds the operating system.

Talk with ProteusX →