01
assistant with context
ginny starts from the course, material, and schedule you selected instead of guessing which part of your day matters.
delegate
An assistant that shows its work.
ginny helps move an academic task forward while keeping the scope, approval, and result visible. It behaves like a careful collaborator, not an invisible operator.
a visible control plane
Helpful automation needs readable boundaries.
02
MCP connections
Connect approved tools through an explicit Model Context Protocol surface. Each connection names what it can read and do.
03
tool calling
See the proposed tool, inputs, and expected result before an action leaves the conversation.
04
reminders
Turn a useful plan into a timed nudge that is tied to a real course moment, not a generic productivity streak.
05
background jobs
Longer work appears as a job with status, source scope, and a return point when the result is ready.
06
approval gates
Sensitive or outward-facing actions pause for a clear yes. No implied consent hidden in a helpful sentence.
07
history and permissions
Review the conversation trail, tool results, active jobs, and access grants in one auditable place.
history you can inspect
Every delegated task leaves a useful trail.
Return to a completed job, review the input and result, adjust a permission, or reuse a plan. ginny keeps the assistant relationship legible over time.
- 09:12
source review
Completed · 3 passages linked
- 09:14
reminder proposal
Awaiting approval · calendar.create
- 09:20
study plan
Scheduled · returns after studio