Loading...
×NanoClaw runs agents in containers and messages you in your chat app. See a planned morning briefing of X ideas that become Tareno drafts only after you reply, and what is unconfirmed.
Register Tareno as a remote MCP server for your NanoClaw group and configure its gateway credential. Verify a read-only call first; Tareno has not recorded an authenticated end-to-end test of this combination. Then use scheduled tasks to propose ideas in chat, saving drafts and requesting publication only after your approval.
Last reviewed 2026-10-26 · Markdown version for AI agents
Some people want their drafting assistant to find them, not the other way round: a message at half past seven with three ideas, a reply, and a draft waiting by the time coffee is ready. NanoClaw fits that shape because it lives in your messaging apps and runs agents on a schedule inside isolated containers. Tareno would be the place where the chosen idea becomes a draft and where any time request waits for approval. The honest part is the connection. NanoClaw documents native remote Streamable HTTP registration per group, with credentials managed separately by its host-side gateway. The authenticated Tareno connection still needs to be checked in your installation. This page describes the workflow and what to test.
Imagine a consultant who keeps approved notes in a shared folder that her NanoClaw agent can read. Every weekday at 07:30 the agent messages her three X topic ideas in her chat app, each with a sentence on why now. She replies with a number. The agent writes a post within 280 characters from her notes and shows it in the chat. When she says yes, and only then, it would use Tareno to confirm her X account with list_accounts and save the draft with create_drafts. This works only once a connection has been confirmed.
Follow the NanoClaw overview to register https://tareno.co/api/mcp with --url for the intended group and configure its gateway credential. Run the read-only check before a recurring task saves anything.
NanoClaw agents run in containers with a limited view of the filesystem. Share one folder of notes you are content to see quoted in public, and nothing else, so the container never reads material you would not post.
Ask for a morning task that messages you ideas and saves nothing. State the rule in the instructions: no draft is created until you reply with the number of an idea.
Once you have registered a server for the agent group following NanoClaw's tools page, ask it to call list_accounts. If it cannot reach Tareno, it should say so and not guess.
Reply with your choice, read the proposed post in the chat and say yes. The agent then verifies the account with list_accounts and files the text via create_drafts.
Say which day, time and IANA zone you want; schedule_posts creates a pending action that waits for you in the dashboard.
Use Tareno to list my connected social accounts with platform and account name. Read only: do not create, schedule or publish anything. If you cannot reach Tareno from this container, say so plainly and tell me which step of the setup seems to be missing.Every weekday at 07:30, read the notes in the shared folder [notes] and send me three topic ideas for X in this chat, each with one sentence on why it fits today. Do not save anything to Tareno until I reply with the number of the idea I want.I choose idea 2. Write an X post within 280 characters from my notes, show it here and wait. When I say yes, use Tareno to confirm my X account [handle] and save the approved text as a draft, then return the draft ID and the text.Use Tareno to list my drafts and pending actions and tell me what is waiting for me, with the account and the time requested for each one. Do not approve, edit or delete anything, and tell me if the list is empty.Take the draft [draft ID] and ask Tareno to schedule it for [tomorrow 08:30] in [Europe/Berlin]. Return the action ID and remind me that the request still waits for my approval in the Tareno dashboard.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: X API documentation: create a post, read on 2026-10-24. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
A `list_accounts` reply from inside the container that shows your X handle. A successful authenticated reply proves tool access; confirm the intended profile before creating drafts. If no profiles are returned, check your connected accounts in Tareno separately from authentication.
NanoClaw, the container-based assistant that runs agents through Anthropic's Agent SDK. NemoClaw is NVIDIA's separate project with its own MCP documentation, and its steps do not apply to this page.
A scheduled task running unattended should only read and message. Saving a draft is a write, and even a draft clutters your account if the agent saves one every day. Waiting for your reply keeps the decision with you.
From a folder you share with its container. NanoClaw isolates each agent's filesystem, so choose a folder of approved notes and check that the agent group cannot see other directories.
You can ask, but Tareno holds each scheduling request as a pending action that you approve in the dashboard. That is deliberate: a recurring task should draft and propose, and a person decides what goes public.
No. Saying yes in the chat only saves a draft. Releasing a time request still happens in the Tareno dashboard, and `get_action_status` reports what X did afterwards.