AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

  • REST API guide
  • Authentication
  • API reference
  • MCP (AI agents)
  • SDKs
  • Quick actions

Webhooks

  • Overview
  • Quickstart
  • Events
  • Payloads and headers
  • Security and signing
  • Delivery and retries
  • Managing via API

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference
Module reference

Module guide

Habits

Track repeating routines with streak and at-risk detection.

Open module/habits
personal

Overview

A per-user habit tracker with a configurable target per period. The deterministic streak calculator reports current, longest, and 30-day rolling totals, and habitsAtRisk() flags anything whose streak will break today unless you hit its target.


Highlights

The capabilities worth knowing before you dive in.

  • Daily or multi-day targets (targetPerPeriod, periodDays)
  • Current streak, longest streak, and 30-day completion sparkline data
  • An at-risk endpoint surfaces habits one check-in away from breaking
  • Per-user scope, so teammates never see each other's habits

Important to know

Limits, permissions, and sharp edges to keep in mind.

  • Streak math is UTC-day based. If you travel across timezones, check-ins near midnight can surprise you.
  • Archiving a habit preserves its history but hides it from active lists.

How to use it

The primary workflow, start to finish.

  1. 1Create a habit with a target and period (for example, 1/1 daily, or 3/7 three times a week).
  2. 2Check in each time you complete it. Check-ins are idempotent per day.
  3. 3Review the at-risk list every evening to protect your streaks.

FAQ

Can I track habits across a team?
Not today. Habits are per-user by design so no one feels monitored. Shared team rituals live in Cycles and Goals.
Why did my check-in land on the wrong day?
Streaks are calculated on UTC days. A check-in close to midnight, particularly while travelling, can therefore fall either side of the boundary from where you expect it.
If I stop a habit, have I lost the record of it?
No. Archiving hides a habit from the active list and preserves its history, so the streak you built remains readable even though the habit is no longer being tracked.

Automate this module

Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
All modules
Was this page helpful?

On this page

  • Overview
  • Highlights
  • Important to know
  • How to use it
  • FAQ