A personal operating layer

The context behind your work, finally in one place.

Afe connects the tools you already use, keeps a living timeline of what happened, and asks the smallest useful question when your judgment is the missing piece.

Question-first Evidence attached You stay in control
afe / now 09:41
Tuesday, 14 October

Good morning, Chiranjeevi.

2 need you now
NOW8 min ago

Your deployment is green. What should Afe carry forward?

The PR merged, but the Jira ticket is still In Progress.

AKeep it open for verification
BClose it with the merge
Why now?2 sources attached
INBOX

Meeting brief ready

3 decisions from Slack and Calendar

SHELF

Resurfaced note

“Incident review checklist” · 4 months ago

Connected contextGSGHJ+ notes
Evidence before confidence
Memory stays in time

Bring the context you already have

S Slack M Gmail 31 Calendar GitHub Jira Notes

The Afe loop

Less managing. More knowing what to do next.

Afe is built around a simple loop: observe what changed, ask when your intent is unclear, and remember the answer with its source and scope.

01

Observe quietly

Signals from Slack, GitHub, Gmail, Calendar, Jira, and your notes become a time-aware record—not another noisy feed.

Source events · timestamps · provenance
02

Ask with purpose

When the right next step depends on you, Afe asks a focused multiple-choice question instead of making a guess.

Small decisions · clear options · later
03

Remember in time

Your answers become scoped, inspectable events. Afe can resurface the reasoning when a future moment makes it useful.

Append-only history · corrections · outcomes

Attention, with a reason

Not everything deserves a notification.

Afe gives every item a place and a reason. Urgent questions can interrupt. Normal work waits in Inbox. Useful context can rest in Shelf until it becomes relevant.

See the trust model
N
Now

Needs your judgment today

Deployment verification · due 14:00

2
I
Inbox

Review when you have a minute

Meeting brief · 3 decisions grouped

5
S
Shelf

Useful later, quiet for now

Incident patterns · resurfaced from notes

12
Decision historyAll sources⌄
Today · 09:33

Keep deployment ticket open

Recorded from your answer · project: payments-api

Decision
Today · 09:25

PR #1842 merged

GitHub · linked to payments-api

Observed
4 months ago

Incident review checklist

Obsidian note · resurfaced because it is relevant

Resurfaced

Memory that stays honest

Nothing important gets flattened into one magic summary.

Afe keeps observations, questions, answers, corrections, and outcomes as a timeline. You can follow the thread, see the evidence, export your history, or delete it.

✓ Original events stay visible✓ Scope can expire✓ Corrections add context

Built for trust

Capable enough to help. Bounded enough to rely on.

Your history is yours

Inspect, export, and delete the events Afe keeps about you. Nothing is hidden behind an “AI memory” label.

Evidence comes first

Material questions and recommendations show the source, timestamp, and relevant change before asking for trust.

Actions need permission

Afe can prepare a safe action, but it cannot write to your tools without policy checks and your explicit approval.

Your context, everywhere

One assistant across the devices and clouds you choose.

Afe is designed to be cloud-agnostic and multi-platform from the start: the interaction surface stays light while your context can scale in the cloud.

One context, every screen6 platforms
aAfe contextcontinues with you
macOSDesktop
iiOSPhone
iPadOSTablet
WindowsDesktop
AndroidPhone
LinuxDesktop

Early access

Build a better relationship with your own context.

Tell us what you want Afe to notice first. We are building the product with knowledge workers who want fewer tabs, fewer interruptions, and better continuity.

Your details are used only for Afe early-access contact.