[FEATURE] Automatic Account Wake-Up for Active or Allocated Session Hours

[VedantBhayani]

Perfect — thanks for the reference. I’ll rewrite the feature request exactly in that structure, clean, detailed, and ready to paste into a Google feature request form. No fluff, no policy landmines.

---

Feature Description

Automatic Account Wake-Up for Active or Allocated Session Hours

Add an automatic account wake-up mechanism that ensures a user’s Google Antigravity account becomes active when allocated or paid session hours are available. This prevents session time from being consumed while the account is idle, suspended, or in a sleep state where the user cannot actively use the service.

---

Use Case

Users who rely on session-based compute (e.g., scheduled workloads, long-running experiments, or time-limited access) may temporarily step away or experience account sleep due to inactivity. When this happens, session hours can continue to elapse without allowing interaction or productive use.

This feature would:

• Prevent loss of allocated or paid session hours
• Allow scheduled or reserved sessions to start reliably
• Reduce the need for constant manual monitoring or re-authentication
• Improve fairness and usability of session-based billing

The feature is especially useful for users in different time zones, users running overnight or delayed jobs, or users who experience brief inactivity-triggered sleep states.

---

Proposed Implementation

Possible implementation options include:

• An “Auto Wake-Up” user setting that, when enabled, automatically reactivates the account if session hours are available

• Wake-up triggers based on:

  • Remaining allocated or paid session hours
  • Scheduled session start times
  • Background jobs or reserved compute becoming available

• Optional safeguards such as:

  • Time limits on automatic wake-ups
  • Notifications when an account is automatically reactivated
  • Idle timeout reset only when a valid session is active

This functionality could be implemented at the session manager or scheduler level without requiring user interaction at the moment of wake-up.

---

Compliance Consideration

Please confirm:

• [YES] This feature is for personal development use
• [YES] This feature does not violate or circumvent Google’s Terms of Service
• [YES] This feature is not intended for commercial resale or multi-user access

---

Alternatives Considered

• Manually checking and reactivating the account before session expiration
• Setting external reminders or alarms to prevent inactivity
• Keeping the session artificially active (inefficient and unreliable)

These workarounds are inconvenient, error-prone, and do not fully prevent session-hour loss.

---

Additional Context

This request is focused on preserving usability and fairness of allocated session time, not bypassing limits or increasing access beyond what is already granted. The goal is to ensure that session hours are usable when available, rather than lost due to automatic inactivity handling.