<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development Environment</title><link>https://blog.ast.moe/en/tags/development-environment/</link><description>Recent posts: Gorimuchu</description><generator>Hugo</generator><item><title>I created ctx-sync, a CLI tool that shares development context across multiple sandboxes.</title><link>https://blog.ast.moe/en/blog/2026-09-23-3/</link><pubDate>Wed, 23 Sep 2026 22:37:00 +0900</pubDate><guid>https://blog.ast.moe/en/blog/2026-09-23-3/</guid><description>&lt;p&gt;When you develop by running multiple sandboxes simultaneously, it’s convenient that each environment is isolated, but it can become unclear what the other sandboxes are doing.&lt;/p&gt;
&lt;p&gt;For example, suppose you conduct research and decide on a design approach in one sandbox, then begin implementation in another. The new sandbox has no prior conversation, so you don’t know why that approach was chosen or what issues remain unresolved. As a result, you may end up repeating the same research or re‑examining decisions that have already been made. It can also happen that one worker unintentionally edits a file another worker is working on, causing their work to clash.&lt;/p&gt;</description></item></channel></rss>