Repository navigation
Social: the owner connects Threads, Facebook (+Instagram), LinkedIn and X #5625
Description
Owner task. The agent can post to a network only after the owner connects it; today none is connected.
Where: the connect card on the app profile (https://t.me/t27ai_bot?start=app_profile); for Facebook choose the page Trinity S³AI. The CRM's new Social networks panel (https://github.com/gHashTag/999-multibots-telegraf/pull/3396) shows each network's state live.
No ## Boundary: this is not a bee task, the consent screens are the owner's to press.
Acceptance criteria
-
social_statusshows Threads connected -
social_statusshows Facebook connected, with the Instagram account under it -
social_statusshows LinkedIn connected -
social_statusshows X connected (refresh token held) -
tri metareports the page id 1265495276656648 and no missing app key
Activity
gHashTag commentedon Oct 2, 2026
#3396 and #3407 merged; vibee-render live at b6ea6a8. Live social_status: apps 4/4 configured, networks 0/4 connected. Reminder with the connect link sent to the owner (message 1761).
gHashTag commentedon Oct 7, 2026
Reopened 2026-10-07: the bulk close of issues without a
## Boundarysection was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.tri-claw commentedon Oct 8, 2026
The Queen cannot take this issue yet. A bee starts only on an issue whose body has every section below, and this one lacks:
- specs/x.t27); without it the Queen reserves nothing and no bee can take the issueFR-001: ... MUST ...exit 0, or a backticked commandShe tried to write them 2 times and could not (last: not a task: The issue describes an owner manual task (pressing OAuth consent screens) with no code changes in this repository; CANDIDATE PATHS is empty and the issue explicitly states it is not a bee task.). Add them and the next round takes it. The rule is
specs/policy/issue_shape.t27.