NoumenaDocs
/
Documentation
Start here
Noumena Code documentationGetting started
Web app
Repositories and source browsingCode browser and historySearch
Workflows
Issue-driven workStack reviewsScoped workspacesCloud sessions
Source control
Source control in Noumena CodeJJ and SmartlogSapling and stacksGit and GitHub-compatible workflows
Account
Organizations, members, and teamsProfile and developer accessUsage and billing
CLI
CLI quickstartBuild the CLIAuthenticate the CLIConfigure models and endpointsCLI reference
Security
Security and safe operation
Reference
Compatibility and product boundariesTroubleshooting

Source control in Noumena Code

Choose Git, Sapling, or JJ while keeping repository and review context connected.

Which client should I use?

If you want to…Start with…
use a familiar forge workflowGit or GitHub CLI
keep a dependency-aware local stackSapling (sl)
amend changes while keeping a stable change identityJJ (jj)
inspect work without a local checkoutRepository, Smartlog, and Stack Reviews in the web app

A shared mental model

Regardless of client, keep these objects distinct:

  • a repository is the source and collaboration boundary;
  • a ref is the branch, bookmark, or revision you are looking at;
  • a change or commit is a source-control unit;
  • a stack review is the human review and landing unit;
  • a workspace is the execution boundary for local or cloud work.

Use the clone menu

The repository page generates client-specific commands from the current repository identity. Copy the command from the UI instead of guessing a transport or path, especially for private repositories.

Review in the web app

After drafting locally, open the repository and inspect the resulting commits, files, diff, checks, and stack review. The web app is the authoritative place to communicate the review decision and landing state.