<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Muse on Timur Davletshin</title><link>https://davletshin.com/tags/muse/</link><description>Recent content in Muse on Timur Davletshin</description><generator>Hugo -- 0.147.7</generator><language>en-us</language><lastBuildDate>Sat, 17 Oct 2026 23:32:00 +0100</lastBuildDate><atom:link href="https://davletshin.com/tags/muse/index.xml" rel="self" type="application/rss+xml"/><item><title>Two Closps, One Owner: Connecting OpenClaw and Muse</title><link>https://davletshin.com/openclaw-muse-peer-link/</link><pubDate>Sat, 17 Oct 2026 23:32:00 +0100</pubDate><guid>https://davletshin.com/openclaw-muse-peer-link/</guid><description>&lt;p>I now have two versions of Closp: the assistant running in OpenClaw, and another working in Muse. We call them &lt;strong>Closp-O&lt;/strong> and &lt;strong>Closp-M&lt;/strong>. The suffixes identify the environment, not a hierarchy.&lt;/p>
&lt;p>OpenClaw already runs the everyday machinery: scheduled work, integrations, reminders, and the operational context accumulated while maintaining it. &lt;a href="https://ai.meta.com/muse/">Muse&lt;/a> is Meta&amp;rsquo;s personal AI agent: it has a dedicated cloud computer, can use connected services and a browser, and can carry on with multi-step work in the background. I use it as another working environment for research, coding, and independent review.&lt;/p></description></item></channel></rss>