Loading...
NanoClaw/TarenoNanoClaw runs agents in isolated containers and connects them to your messaging apps.
NanoClaw / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
NanoClawIllustrated demo · no live account
Register https://tareno.co/api/mcp for the intended NanoClaw group with ncl groups config add-mcp-server, using --url for remote Streamable HTTP. Configure the Tareno credential in NanoClaw’s gateway and grant only that group access. Restart the group and ask for list_accounts. The setup is documented; confirm the authenticated call in your installation before saving drafts.
NanoClaw runs each agent in a Linux container with filesystem isolation and Docker as the default runtime. A host process routes messages from your chat apps to the container and delivers replies. Channels such as Telegram are added with skills like add-telegram.
Register the hosted Tareno endpoint with the remote --url option for the intended group. Use the group ID from your NanoClaw installation; this config applies to that group, rather than every agent. A bridge is not required for the documented native Streamable HTTP path.
Configure the Tareno API credential through NanoClaw’s host-side credential gateway using an Authorization Bearer header for tareno.co, then grant access only to the intended group. Use the gateway’s credential setup, not a raw key in --headers, --env, a URL or a prompt. Native remote registration does not itself complete Tareno OAuth.
Restart the group so its next container receives the new MCP configuration. Ask it to call your connected accounts without making changes. An authenticated empty result can mean no social accounts are connected in Tareno; a 401 means authentication still needs attention. Do not start drafts until you can identify the intended profile.
ncl groups config add-mcp-server --id "<group-id>" --name tareno --url https://tareno.co/api/mcpncl groups restart --id "<group-id>""url": "https://tareno.co/api/mcp"Input
Provide the approved source and audience.
Review-ready drafts
Use Tareno and compare the returned draft IDs.
Approval in Tareno
Review text, media, account, and time in Tareno and approve.
Once registration, gateway access and a read-only call succeed, the same group can turn approved notes into social drafts. Keep the briefing, your choice of an idea, and the publishing decision as distinct steps.
NanoClaw can run a scheduled task and message you the result in your chat app. A morning briefing of topics for the day, with draft posts for you to react to, fits that shape: you answer in the chat, and drafts go to Tareno only after you say yes.
Because each agent runs in its own container with a limited view of the filesystem, you can keep the notes it reads separate from the rest of the machine. That suits a founder who wants a drafting agent to see a folder of approved notes and nothing else.
NanoClaw adds capabilities by copying skill code into your fork. That means the connection to Tareno would be code and config that you can read and review, which is a different trust model from a hosted connector, and it puts the burden of correct setup on you.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
OpenClaw and Hermes Agent have Tareno skills published on ClawHub. NanoClaw offers a per-group MCP configuration and a host-side credential gateway. Choose the runtime you already operate, follow its own authentication instructions, and check the actual tools returned by Tareno before starting recurring work.
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:
Yes. NanoClaw documents both local stdio servers and remote Streamable HTTP servers. Use ncl groups config add-mcp-server with --id, --name and --url for Tareno. The group receives the server at its next container start, and credentials are configured separately in the gateway.
No. NanoClaw is the container-based assistant that runs agents through Anthropic's Agent SDK. NemoClaw is NVIDIA's project with sandboxes and its own MCP pages, which accept Streamable HTTP endpoints. Do not mix the two when you follow a guide.
No authenticated NanoClaw-to-Tareno test has been recorded. The registration syntax is documented, so you can set up the group and its gateway credential, then test list_accounts. Confirm the returned profiles before a task creates any drafts or requests a posting time.
The Tareno credential and the group’s permission to use it. NanoClaw’s gateway stores the credential on the host and injects authentication into allowed outgoing requests. Verify the gateway, the group assignment and the remote client’s proxy use before expecting authenticated tools.
From your own fork. Skills such as the one for Telegram copy the required modules into it, which means you can read what was added. Other model backends, such as Codex or Ollama, are described as skills too.
Not through Tareno. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches X until you approve it in the dashboard. The agent can only report that the action is pending and read its status.
Sending yourself ideas is. Saving a draft is a small step, and Tareno still holds any time request until you approve it. Keep the agent's instructions explicit that it must wait for your reply before it saves anything.
Once a connection exists, the agent would usually call `list_accounts` to confirm the destination, then `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, and `get_action_status` shows what became of it.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.