Atmos Pro Logo

Atmos Pro

ProductPricingDocsBlogChangelog
Create Workspace
← Back to Changelog
FeatureFix

Stay Signed In, and Set How Long a Session May Last

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

|September 25, 2026

Older

Follow Deployments and Releases by Email

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

Erik is the founder of Cloud Posse and creator of Atmos. With over a decade of experience helping teams adopt Terraform at scale, he is passionate about open-source infrastructure tooling and developer experience.

Book a Meeting
Atmos Pro Logo

Atmos Pro

The fastest way to deploy your apps on AWS with Terraform and GitHub Actions.

GitHubTwitterLinkedInYouTubeSlack

For Developers

  • Quick Start
  • Example Workflows
  • Atmos Documentation
  • Register for Office Hours
  • Join the Slack Community

Enterprise

  • Trust Center
  • Procurement
  • Pricing
  • Contact Sales

Company

  • Support
  • About Cloud Posse
  • Security
  • Blog
  • Media Kit
  • Try our Newsletter

Legal

  • SaaS Agreement
  • Terms of Use
  • Privacy Policy
  • Disclaimer
  • Cookie Policy

© 2026 Cloud Posse, LLC. All rights reserved.

Checking status...
If Atmos Pro sent you back to the sign-in page every morning, or partway through a long day, that is over. Your sign-in used to be tied to the GitHub token behind it, which expires after about eight hours. Any break longer than a few minutes across that mark ended the session, and returning to an open tab could end it too. Atmos Pro now renews that token before it expires and recovers it when you come back after a break, so your session lasts until it reaches its limit.
That limit is now yours to set. On an Enterprise plan, the Security tab has a Session lifetime setting: the longest a sign-in may last, measured from the moment you signed in. Sessions do not extend with activity.

Session lifetime

The longest a sign-in may last, measured from when the user signed in. It applies to anyone whose current workspace is this one, and it also caps how long MCP refresh tokens issued for this workspace stay valid between uses. Sessions do not extend with activity.

Maximum session lifetime
Existing sessions pick up the new limit the next time they switch into this workspace or sign in.

How It Works

Pick one of seven presets: 1 hour, 8 hours, 12 hours, 24 hours, 7 days, 14 days, or 30 days. The default is thirty days. The limit applies to anyone whose current workspace is this one, so a member who switches into a workspace with a stricter policy picks up that policy from their original sign-in time, and is asked to sign in again if their session is already older than it allows. Sessions on other plans keep the thirty-day default.
The same policy caps how long an MCP refresh token issued for the workspace may sit unused, so agents connected through Claude Code or the claude.ai connector follow the workspace's rules too. Existing tokens keep their current lifetime until they next refresh.
Every change to the policy is recorded in the workspace audit log.