Moving from AI Interaction to Orchestration

Last year, I was talking to AI. This year, I’m beginning to orchestrate it.

Although Orion has become my primary AI tool, I am working more with Gemini and Copilot as secondary tools. Gemini is a strong resource for exploring all that Google has to offer. I am just starting with Agents, and the Antigravity tool captured my attention as a possibility to get my monster Gmail archive under control.

After a successful installation of Antigravity (it runs locallly), my first test generated a tiny HTML Timer. It’s just a tab I open in my browser, but it’s a 2-hour timer that counts down ow long I have been sitting so I remember to move! First assessment: not very fast, fascinating to watch as Aggie (Antigravity) shows each step it’s taking, and solid delivery. Passed the first test, so I moved on.

I spent an afternoon doing a bit of digital archaeology with my email, and I identified the flood of newsletters I subscribe to as my first category to attack. My goal was to get a daily summary to let me quickly see which ones earned a full read and which ones got archived for bedtime reading. What I ran into first was a familiar kind of resistance setting up connectivity to my Gmail through Google Cloud Console.

For hours, I hit the same wall – one I was somewhat familiar with since I have done this before.

Google’s security wasn’t letting the AI in. The handshake kept failing.

Instead of giving into frustration, I took a lunch break.

When I came back, I shifted into full detective mode.

I realized I wasn’t trying to fix a single problem.

I was assembling a system.

  • A local server holding keys and permissions
  • An agent (Aggie the Antigravty Agent) acting as a conductor
  • A browser-based sub-agent that could navigate systems the way I would

Once I saw it that way, things began to click. With Gemini’s help, we parsed the error message and found a path problem that resolved the issue.

Aggie is now connected to my email. A few prompts later, and results appeared.

The results weren’t dramatic in a flashy sense—but they were meaningful.

The agent could:

  • check Gmail for “unsubscribe” to identify the newsletters
  • Summarize by sender and content
  • Tag as Summarized
  • Move to archived at end of week

How it helped:

  • Reduced the clutter in the inbox
  • Identified material that was duplicated across newsletters
  • Automaticaly condensed the reading area each week to keep focus on current material.
  • Put several hours a week back into my schedule to use for production.

I’m still early in this work.

But it feels like a turning point. Agents will definitely have a future here.

Less prompting.
More orchestration.

And a different kind of leverage entirely.