atmosphere/atmosphere

Portable AI agent runtime for the JVM. One @Agent class runs on Spring AI, LangChain4j, Anthropic, or 9 more behind one SPI. Token streaming, tool calls,...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 18th, 2026
Created on June 30th, 2010
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 762
Total Stargazers: 3,815 (+0)
Total Subscribers: 224 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.6 hours
Mean response time: 477.5 days
90th percentile: 2595.8 days
Tracked items: 69

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 103 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • legacy (42)
  • Enhancement (5)
  • dependencies (5)
  • 2.4.0 (4)
  • 2.3.3 (2)
  • 2.3.4 (2)
  • 3.1.0 (2)
  • Help Wanted! (2)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

Atmosphere is a portable AI agent runtime for the JVM that abstracts away the underlying AI framework through a service provider interface.

The problem Atmosphere solves is the fragmentation across AI agent frameworks and the difficulty of switching between them or supporting multiple backends simultaneously. It provides a single @Agent class annotation that works across Spring AI, LangChain4j, Anthropic, and over nine other frameworks without requiring code changes. The runtime handles token streaming, tool invocations, human approval workflows, and governance policies uniformly across all supported backends.

Developers should choose this tool if they want to avoid vendor lock-in to a single AI framework or need to support multiple frameworks in the same application. It suits projects where framework flexibility matters more than deep integration with a specific ecosystem, and where teams need standardized governance and approval mechanisms across agent deployments. The abstraction layer means you can write agent logic once and deploy it against different backends, making it valuable for organizations evaluating multiple AI platforms or planning future migrations.

The project shows consistent development activity with regular commits across multiple areas of the codebase. Pull requests are reviewed and merged steadily, indicating active maintenance. The repository maintains documentation and examples alongside core functionality. Issue tracking shows engagement with user questions and feature requests. The breadth of supported frameworks and protocols suggests the maintainers are actively expanding compatibility as new standards and platforms emerge in the AI agent space.