Moiravo is in development. There is no public download, production workspace, or self-serve installation to complete from this website. The workspace on the home page is an illustrative product preview.
1. Choose a piece of work with continuity.
Pick a question or outcome that will outlive a single conversation: investigating a product problem, planning a change, or working through an architectural choice. Keep the first example small enough that you can describe its purpose in a few sentences.
A useful thread has a reason to exist. “Improve onboarding” is a direction. “Understand where new users stop and choose one improvement to test” gives the work a clearer center.
2. Write a compact starting brief.
Before choosing a tool or an agent, record what matters to the outcome:
- Intent: What are you trying to change or understand?
- Current view: What do you know, and which sources support it?
- Boundaries: What should remain outside this effort?
- Open question: What is the next uncertainty to resolve?
- Evidence: What would make the result useful enough to rely on?
The brief should help you resume the work. It does not need to reproduce every message that led to it, and it should retain uncertainty where the answer is not settled.
3. Explore the product direction.
Use the illustrative workspace to see how threads, working material, and status can sit together. The preview uses example content. It does not connect to your tools, run agents, or persist a real project.
The current local foundation supports thread capture, entries, working briefs, and source-linked context records. The intended end-to-end workflow adds scoped execution, branches, and handoffs across qualified tools. Those later capabilities are not available as a public product.
4. Request early access.
Use the access form to leave an email and, optionally, a short description of your work. Details such as the tools you already use and the point where you lose context are helpful. Please leave out credentials, private customer data, and confidential working documents.
We review requests as previews become suitable for evaluation. Submitting the form does not create an account or guarantee an invitation. Setup instructions, limitations, and any participation terms will be provided before you choose to use a preview.
Read next
Threads and sessions explains the central distinction. Development status describes the present boundary of the product.