Post to X without living on X.
CoreLayerEngine writes, trims and schedules your X posts through the official X API v2 — single posts or true reply-chained threads — at the slot your audience actually shows up. You approve; the engine posts.
Where this stands, plainly: posting to X from your own account is not switched on yet, and there is no review by X to wait on — media upload sits behind a paid API tier that we have to hold. Until we hold it, approved posts and threads wait in your queue, written, trimmed and slotted, and you post them in one tap from your phone.
What can it actually post to X?
One post or a real thread. Both go out through X's official v2 API with your own OAuth 2.0 token — no browser automation, no session cookies.
Single posts
The engine drafts to X's 280-character budget and trims on a word boundary if a draft runs long, so nothing gets cut mid-word. Images are uploaded through the v2 media endpoint when your X API tier allows it.
Native threads
The thread builder splits a longer idea into parts, and each part is posted in order and reply-chained to the one before it with in_reply_to_tweet_id. That is a real X thread, not numbered posts fired in parallel.
What happens if media upload is refused?
media.write scope and a paid API tier. If your account cannot upload, the post degrades to text-only and logs why, rather than silently losing the slot. You will see it in the run log — we would rather tell you than pretend.Does it decide what to post?
Frequently asked questions
Does CoreLayerEngine post to X automatically?+
Not yet. The adapter is built against the official X API v2 and takes your own OAuth 2.0 connection, and the engine drafts and schedules as usual — but direct publishing is not switched on here, and the step left is ours: X charges for the access tier media upload needs. Until we take it up, an approved post waits as a finished draft in your queue and you send it in one tap.
Can it post real X threads?+
Yes. The thread builder splits your idea into parts within the 280-character limit, then posts each part reply-chained to the previous one using X's in_reply_to_tweet_id. The result is a native thread, in order, from your account.
Does it use unofficial automation or scraping?+
No. Only the official X API v2 with a token you granted. No browser bots and no session cookies. Where the API restricts something — image upload needs a paid tier we have not taken up, so an approved post waits as a draft you send in one tap until we do — the page says so instead of implying it works.
What happens to images on a free X API tier?+
The v2 media upload needs the media.write scope and a paid X API tier we have not taken up. On tiers that cannot upload, the adapter degrades to text only and the run log records the reason rather than failing the run. Until the tier is taken up, an approved post waits as a finished draft you send in one tap, picture and all.
Does X performance change what the engine writes next?+
Yes, and only for X. Outcomes feed the learning loop per channel, so what wins on X shapes future X drafts and posting slots without distorting your LinkedIn or Instagram copy.