Authorise a source
A supported provider shows the permissions requested before Habit can read the selected account data.
From connected context to a prepared day.
Habit follows a legible path: you choose the sources, it assembles relevant context, prepares a brief or proposal, and keeps consequential actions behind a visible decision boundary.
Step one
Choose the context Habit may use.
Connections begin with provider authorisation, not assumed access. You decide which supported sources to connect and can disconnect them later.
Keep the boundary visible
Connected sources remain distinct, so a calendar, mailbox or document source does not quietly become universal access.
Pause or disconnect
You can stop a connection when it no longer belongs in your assistant’s working context.
Step two
Assemble signals without hiding the gaps.
Habit can bring together schedule, screened messages, recent meetings, people and relevant memory. If a source is unavailable, the experience should show that limitation instead of pretending the view is complete.
The goal is not to copy every connected item into one larger feed. Habit looks for the signals that change what you need to know: a reply awaiting a decision, preparation missing from a meeting, or a commitment that has not yet found a place in the day.
Where possible, surfaced items retain a path back to their source. That makes the brief inspectable and gives you a way to correct the context behind a suggestion.
Step three
Build continuity you can inspect and correct.
Useful assistance depends on continuity, but continuity should not become an invisible pile of assumptions.
Stated preferences
Preferences you express can help shape later briefs and proposals without turning a single interaction into a permanent rule.
Relationship context
Relevant people and prior interactions can stay attached to the work where that context helps you make a decision.
Provenance and correction
Memory is designed to retain source context and support correction and management rather than turning an observation into an unchangeable rule.
Step four
Prepare before proposing.
Habit can turn assembled context into a daily brief, an attention item, a reminder, a reply draft or a structured proposal.
Preparation is useful when it reduces the distance between noticing and deciding. A draft should carry enough context to review. A schedule suggestion should say what would change. A brief should separate facts from recommendations.
Generated brief prose is checked against computed facts; when that check does not hold, Habit can fall back to a deterministic summary rather than present unsupported prose as settled context.
Step five
You decide what happens next.
A request becomes a reviewable proposal. You can approve it, modify it or decline it before a consequential change is made.
Review the proposed action
The intended change and its source context stay visible at the decision point.
Modify or decline
A prepared response is a starting point. You can edit the wording or decide the action should not happen.
Choose bounded automation
Eligible calendar additions can run only after you deliberately opt into that specific standing authorisation; updates and deletes remain review-gated.
At any point
Keep control of permissions, memory and momentum.
You can review permissions, pause the assistant, disconnect a provider and use the memory settings available in the product as your needs change.
An assistant should become more useful without becoming harder to understand. Habit is designed so the controls around context and action remain part of the product, not a footnote behind it.
Review Habit’s security controlsQuestions
What happens around the edges of the flow.
- Do I need to connect everything?
- No. Habit works from supported sources you deliberately authorise. The useful set is the context that supports the assistance you want.
- What happens if a connected source is unavailable?
- The missing source should be shown as unavailable. Habit should not present an incomplete brief as if every source was checked successfully.
- Does Habit store conversation context?
- Relevant conversation context may be retained to support continuity. Verify the exact retention and management controls in the current product rather than inferring them from the category description.
- Can I edit a proposal before approving it?
- Yes. A proposal is reviewable: you can modify the prepared content, approve the intended action or decline it.
- Can I pause Habit?
- Yes. Controls include pausing assistance and disconnecting providers when you do not want new context gathered or prepared.