an x assistant that brings the conversation to you

what a bot can do in X

a focused source list is easier to review than an open-ended feed. tell the bot whose posts matter and what kind of question deserves your attention. it can gather the source posts before suggesting a reply in your dusk bot chat.

composio, the connection service dusk bot uses for apps, lists 84 Twitter actions (catalog version 20261101_00, read 12 november 2026⁴). dusk bot treats 39 of them as reads, 15 as sends and the other 30 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like add post to bookmarks: it waits for your Allow unless you've given that bot a daily amount it may send alone.

composio has no ready-made sign-in for X. connecting it needs your own composio project key and an auth config of your own, added under Settings, API keys. on dusk cloud, ask us first.

connect X

1. open Connected apps in the sidebar.
2. pick X and sign in on X's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your X.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

as of 12 november 2026, this toolkit has no composio-managed sign-in. set up your own composio project key and auth config under Settings, API keys. do not plan a live routine until the connection works and the bot has confirmed the intended x account.

routines to copy

choose a small source list and a single topic before scheduling these. the first two leave x untouched. the third prepares copy in chat, which you can revise without publishing anything.

every weekday at 11, review x mentions for the user id i gave you. bring me direct product questions and reports of something broken, with the original post and a short reason to answer. skip praise without a question. do not like, follow or reply.

every wednesday at 8, read the x list id i gave you for packaging design. pick posts about materials or production constraints, group repeated ideas, and show the posts behind each point. leave opinions labelled as opinions.

every friday at 1, read this week's x posts for the user id i gave you. suggest one follow-up that answers an unfinished question. write the proposed copy in our chat and name the earlier post it builds on. do not publish it.

what it asks you first

publishing posts and sending messages ask you first by default. you can set a daily amount a bot may send on its own, so keep that setting at asking if you want every publication reviewed. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending.³ draft text in your dusk bot chat does not need an x publishing action.

likes, retweets and bookmarks count as sends and ask first. follows, mutes and list changes don't, so keep them out of the allowed list. if you enable any of them, write "ask me before you change anything" into the routine and narrow its allowed action list to the work you actually want.

search and opening a single post aren't available on a read-only connection; opening a post by id counts as a send in dusk and asks first. use the posts returned by mentions, user-post and list reads for the research routines.

what it cannot do

• connect through a composio-managed sign-in. a working custom auth setup is a prerequisite, not a step the routine can skip.
• start a routine when something happens on x: there are no x events, use scheduled reads for these routines rather than promising an immediate mention alert.
• post or follow accounts with read-only permission. permission to research a topic does not give a bot permission to engage with it.
• check mentions on a desktop that is asleep. local runs stop with the computer or app; choose dusk cloud if the schedule must continue while you are away.

choose between listening and publishing

a listening routine should give you the question, its source and why it matters. a competitor monitoring routine can use the same discipline without turning every mention into a reply.

for a publication workflow, see social media posting. decide who checks the wording and which claims need evidence before enabling sends.

avoid a brief full of repeated claims

tell the bot to group posts that repeat the same announcement and keep the original source where it can identify one. a busy thread is evidence of discussion, not evidence that the claim inside it is true. ask for unanswered questions alongside the summary.