Meteor Factory presents

Singularity

Your Agentic Development Environment (ADE). Build features, fix bugs, and evolve your code with AI agents working in parallel.

cross the horizon
singularity ›

01 · The status quo

Stop babysitting terminals.

Comparing Cursor, Devin, Orca or Superset to build software with AI? Everywhere, agents write code, yet you still steer them by reading scrolling text. Singularity, your next development environment, replaces that stream with tickets, a Git graph and review before integration.

The terminalOne agent per tab. To know where it stands, you scroll back up.
The chat in the editorThe conversation grows, context saturates, the diff lands all at once.
The terminal gridFour agents, four streams. Nothing tells you what is done, blocked or ready for review.

Schematic illustrations of common approaches, not screenshots of third-party products.

In Singularity

A board, not a chat thread.

Mission Control puts every request in a column: to do, user action, in progress, done. Each card is a ticket, with its project, its dependencies and the agent working on it.

  • Live agent status
  • “Blocked by” dependencies
  • User action column
  • Several projects, one board
Compare Singularity with other IDEs and ADEs →
Mission Control: to-do tickets, a user action column with “Mark as done” buttons, in-progress and done tickets across three projects.

02 · The ticket

The ticket replaces the conversation.

A ticket brings together a goal, a project, a branch and an agent. The board shows where each ticket stands; its detail keeps the brief, the worktree and the agent timeline.

Three Writing agents in parallel: agent progress, ticket filters and release notes across three Atlas projects.
  1. Live statusThree agents write in parallel, each on its own ticket.
  2. Separate projectsEvery card identifies the project the work belongs to.
  3. Visible dependenciesRelease validation waits for the filters ticket: “blocked by F-4”.
  4. Completed workThe delivery workflow is already completed and remains visible.
Discover Singularity in video
Watch on YouTube

Application captures, demonstration data.

03 · Git

The Git graph, in plain sight.

Agents commit in their worktrees. You follow everything in the built-in Git client: graph, branches, stashes, hooks and conflict resolution.

Atlas Git graph: six branches, two merges, release tags and a stash.
Commit graphBranches, tags and stashes on one graph. Fetch, pull, push, branch and stash in one click.
Git panel: three unmerged worktrees with commits ahead and a “Merge into main” action.
One worktree per agentEach run gets its own folder and branch. Merge it into main, open its graph or browse its files.
Three-pane merge conflict resolution: current branch, incoming source and result.
Conflicts resolved on screenPick block by block or line by line. Nothing is written before you confirm, and you can hand the resolution to a ticket.

Read the Git graph guide →

04 · The cockpit

And everything around the code.

Release Alpha pipeline runs: succeeded, cancelled and failed statuses with job details.

CI/CD pipelines

Follow every GitHub Actions run, job by job, without leaving the app.

Creating a repair ticket for the Release Alpha pipeline, with agent and model selection.

Repair the CI

A pipeline fails? Create a prefilled repair ticket and choose the agent that handles it.

Aperture palette: searching “git” in the active workspace.

Aperture

The palette that finds projects, Git commands and views, or asks Singularity.

General settings: appearance, language and workspace preferences.

Your agents, your rules

Default provider, commit queue, interactive mode: you set the level of autonomy.

05 · In short

The answers that matter.

What is Singularity and its agentic development environment?

Singularity is an Agentic Development Environment (ADE): a desktop application combining an editor, a terminal, Git and a ticket board to manage AI agents. Describe a feature, bug or refactor in a ticket, then select the provider and model that will carry out the task. The board keeps the conversation, the projects touched and the outcome of each run together.

Orchestration coordinates the work: the scheduler considers dependencies, priorities and the concurrent-agent limit when starting ready tickets. You can follow commands, clarify an instruction or stop a run from its detail view. Singularity does not guarantee correct code or delivery without intervention: project checks and review remain necessary. The chosen provider also determines the capabilities and cost of the session. The guide documents these steps, explains how to follow a running agent and distinguishes the possible completion states.

Read the documented orchestration workflow

How does a ticket define an agent’s work?

A Singularity ticket is a unit of work that brings together a request, its context, conversation and result. To fix a login bug, describe the observed behavior, the expected outcome, the relevant files if known and the test that will validate the fix. This gives the agent an explicit scope instead of an endless conversation.

A dependency makes a ticket wait when another change must be integrated first. The ticket preserves its history and can be resumed with an additional instruction. Splitting work this way makes progress easier to track, but does not eliminate reasoning errors or ambiguity: an unclear request still needs clarification or a decision. The guide explains what information the agent receives and how to resume a ticket.

Read about the ticket lifecycle

How do worktrees isolate code before integration?

A Git worktree is a working directory associated with a branch of the same repository. In Singularity, when “Use git worktrees” is enabled, each agent run receives its own directory and branch. The agent changes files, runs project checks and creates commits there without touching uncommitted changes in your main working directory.

At completion, commits are replayed onto the base branch through a rebase. Depending on board settings, the result is integrated automatically or presented in the Review tab; disable auto-merge to retain human approval. File isolation does not guarantee compatible changes: two tickets can introduce contradictory business rules without a Git conflict. When the base advances, the affected interactions need to be checked again before integration. If worktrees are disabled, the agent writes directly into your working tree instead. The guide documents these settings, the integration lifecycle and the limits of parallel work.

Check worktree settings and limitations

Internal experience report — June 8–14, 2026

227tickets shipped
86non-bug tickets
11projects driven
8agents at peak
2,1messages / ticket

Historical figures reported by Meteor Factory, not independently audited. Read the definitions, exclusions and recalculation limitations. Case study and calculation method (October 10, 2026)

06 · Questions

What to know
before departure.

How do I start a first ticket with Claude Code or Codex?+

Install the selected CLI, run claude or codex in a terminal and complete authentication. Check that it responds from your project directory. In Singularity, select the provider and an available catalogue model, or Auto. Then create a small ticket, such as fixing a bug with a test, and review the tests and Git diff before integration. Set up Claude Code: sign-in and models Set up Codex: sign-in and models

What exactly is Singularity?+

Singularity is an Agentic Development Environment (ADE) for building software with AI agents. It combines a code editor, terminal, Git and ticket-based orchestration to build features, fix bugs and refactor multiple projects in parallel.

Is Singularity only for DevOps or SRE teams?+

No. Singularity is for developers and teams building and maintaining software: web and desktop apps, APIs, tests and refactoring. Pipeline monitoring and DevOps tools complement this general-purpose development environment.

Can Singularity prevent AI hallucinations?+

No. Focused context can help limit drift, but guarantees neither the absence of hallucinations nor correct code. Agents can produce false answers, invent information or introduce bugs. Check sources, review changes and run tests before integration.

Is Singularity an alternative to Cursor, Devin, Orca or Superset?+

Yes. Singularity is an alternative to evaluate for AI software development alongside Cursor, Devin, Orca and Superset. Its workflow centers on atomic tickets, parallel agents and isolated Git worktrees, with change review before integration. Compare the tools on your projects and preferred way of working.

Which AI models does Singularity support?+

Singularity orchestrates seven AI providers: Claude Code (Anthropic), Codex (OpenAI), GitHub Copilot, Cursor, Gemini (Google), Mistral and Ollama. Available models depend on the catalogue and your configuration. Sign-in uses the account authenticated in the provider CLI or a key depending on its configuration; Cursor and Mistral also offer a key field. Ollama uses a local or remote endpoint, with a token if required. Provider and data transmission guide

How much does Singularity cost?+

Singularity is a free application for orchestrating development agents. The free plan includes unlimited agents, projects and worktrees, language servers and the Notes plugin. No subscription or credit card is required to use these features. Singularity Licence is the subscription that unlocks paid Marketplace plugins, with a 14-day free trial followed by €24 per month per workstation. The first payment is charged after the trial. It provides access to the Pipelines plugin for CI/CD in the app. Future paid plugins are included at no extra charge. Cancel at any time. The Notes plugin remains included in the free plan; the subscription does not change Singularity’s core features. AI provider costs are separate from Singularity Licence. Singularity does not resell models: neither the free application nor the plugin licence includes paid subscriptions or external model usage. Depending on the provider and model, you use your account or API key and pay the provider directly for any applicable subscription or usage. Your total cost is the optional plugin licence plus any AI provider costs.

Is my code and data kept private?+

Local storage does not mean all data stays on your computer. Configured CLIs may send prompts, file excerpts and tool results needed by the agent to the selected provider, under its terms and retention policies. With a local model served by Ollama on your computer, inference stays local; downloading the model contacts the registry. A remote Ollama endpoint sends requests to the configured server. Check the endpoint and tool permissions: local inference does not guarantee that agent tools work offline. Provider and data transmission guide

Which operating systems does Singularity run on?+

Singularity is available on macOS and Windows. Linux packages are also published.

07 · The humans

Built in France,
close to the code.

08 · The horizon

Cross
the horizon.

macOS · 2.18.125

Also on Windows — Windows x64 · Windows ARM64

Also on Linux — AppImage · x64 · deb · x64 · rpm · x64 · pacman · x64 · tar.gz · x64

Local Ollama: inference on your computer.
Cloud providers receive your prompts and code excerpts. A remote Ollama endpoint also receives your requests.

ClaudeCodex / GPTCopilotGeminiMistral