Skip to content
Muse Atlas
All use cases

Build software

Understand repositories, change code, run tools and validate results.

Concept: build software

What this is useful for

Illustrative tasks you could bring to Muse. The tools and access you provide determine what can be completed.

1

Fix a broken checkout

“Find why checkout fails after an address is entered.”
  1. Trace the relevant code
  2. Reproduce the failure
  3. Make a focused change
  4. Run tests and inspect the page

What you getA proposed fix with checks for you to review.

2

Understand an unfamiliar repository

“Show me where this app handles sign-in.”
  1. Read the project structure
  2. Follow the sign-in request
  3. Identify dependencies
  4. Explain the path through the code

What you getA map of the relevant files and how they connect.

3

Add a small feature

“Let users sort this table by date.”
  1. Inspect the existing table
  2. Follow project conventions
  3. Implement sorting
  4. Check empty and populated states

What you getA reviewable change that fits the existing app.

How the work happens

  1. 1Repository
  2. 2Inspect
  3. 3Change
  4. 4Test
  5. 5Review

What Muse can do

  • Understand a codebase
  • Modify files
  • Run development tools
  • Execute tests
  • Inspect failures
  • Iterate on changes

Which Muse products are involved?

Muse Spark

Understands the repository, reasons about the problem and proposes code changes.

Muse Code

Connects the model to source files, commands and tests so changes can be checked.

Muse Glimmer

Processes permitted code on your own hardware with a compatible local runtime.

See it in practice

Illustrative workflow: Browser-Based Website Development
1. Receive task2. Generate code3. Run application

Browser-Based Website Development

An AI workflow that creates a website, opens it in a browser, inspects the result and makes corrections.

View example
Illustrative workflow: Multi-Agent Product Studio
1. Define brief2. Plan work3. Build in parallel

Multi-Agent Product Studio

Product, frontend, backend and writing roles coordinate on a software project.

View example
Illustrative workflow: GitHub Automation
1. Receive event2. Triage3. Review

GitHub Automation

Triages issues, reviews pull requests and proposes fixes.

View example

What to keep in mind

  • Tests cover only the behavior they check; passing tests do not prove correctness.
  • Review changes before merging, especially authentication, payments or data handling.
  • Tool permissions and a working development environment determine what can be executed.