AI Agents & Orchestration

AI Automation Basics

Last updated 2026-09-07

What's new

2026-09-07
  • GPT-6 Astra (a powerful AI model) can be used as a personal AI operating system (AIOS), acting like a co-founder that knows everything about your life and business.
  • An AIOS combines context (your goals, business, and priorities), connections (tools like email, Slack, and project management), capabilities, and cadence (autonomous agents and automation) to create a powerful second brain.
  • The AIOS can help reduce context switching (jumping between tasks and tools) and offload memory tasks, allowing you to focus on more important work.
  • Free resources and skills, like adaptation, auditing, and links, are available to help set up and improve your AIOS.

Key points

What it is

  • AI automation uses AI to handle tasks needing human-like judgment, unlike traditional automation that follows fixed rules.
  • AI automations are non-deterministic (flexible but unpredictable), while traditional code is deterministic (predictable and easy to test).
  • AI is best for tasks requiring judgment or handling messy information, not for tasks with clear rules.
  • JSON (a text format for storing info) is key for automation, structured like pairs of keys and values (e.g., "item": "shoes").

How to use it

  • Start with workflows (sequences of steps), not AI, to understand how tasks function before automating them.
  • Break down tasks to decide which parts need AI's flexibility and which can use simple logic.
  • Create automations by writing a prompt specifying what the AI should do and where it should work (e.g., locally).
  • Begin with repetitive tasks, like summarizing emails, and give AI agents a brain (AI model), memory (storage), tools, and clear instructions.

Watch out for

  • Avoid automating everything; amplify tasks that work well instead of automating just because you can.
  • AI can be unreliable, expensive, and slow, so only use it when necessary.
  • Plan for failure and test AI automations with real examples before going live.
  • Be specific in your prompts and focus on foundations to avoid common pitfalls.

Tools named

  • Codex (a tool for creating automations), Cursor (a tool for creating automations)

Lesson 1: What is AI Automation Basics and why it matters

AI automation basics means using AI to handle tasks that normally need human judgment, while regular automation follows fixed rules. Think of it like cooking: traditional software follows a recipe step by step, but AI learns from examples and writes its own recipe. This makes AI automations non-deterministic (unpredictable but flexible), unlike traditional code that is deterministic (predictable and easy to test).

Why does this matter for AI development? Because most tasks don't need AI. About 50% of business automations can be built without any AI at all. If a task follows clear rules, use normal automation—it's reliable, fast, and cheap. AI is sometimes unreliable, expensive, and slow, so only use it when you need judgment or the ability to handle messy information. For example, you can create an automation by going to "new automation," giving it a title, and writing a prompt that specifies what you want the AI to do and where it should work, like locally.

The key is to rate the steps, not the whole task. Break down what you want to automate and decide which parts need AI's flexibility and which parts can be done with simple logic. Also, avoid the trap of automating everything in sight—amplify what works, don't automate just because you can. When you do build AI automations, remember to plan for failure, because AI is a black box (unpredictable inside), so test with real examples before going live.

Sources

Lesson 2: How to use AI Automation Basics: step-by-step

AI automation lets you connect tools and data so tasks run without you clicking through them. The most important rule for beginners: do not start with AI. Start with workflows. Before building agents (programs that act on their own), you need to understand how a workflow—a sequence of steps—actually functions. Jumping straight to AI is trying to run before you can walk.

Begin by learning JSON and data types. JSON (a text format for storing info) looks like code, but it's just pairs of keys and values. Think of it like an online shopping order: the "item" key holds the value "shoes," and "price" holds "49.99." Almost every automation tool reads and outputs JSON, so you'll read this structure constantly.

To build your first automation, open a tool like Codex or Cursor and find the automations tab. Creating one is simple: click "new automation," give it a title, and write a prompt. In that prompt, be specific about what you want the AI to do, and choose where it works (like locally on your machine). For example, you could write, "When I add a new row to my spreadsheet, send me a message with the total."

Before building anything, ask what's worth automating and how much to automate. Not every task needs AI. Start with a repetitive task you do daily, like summarizing emails. The core pattern for most agents is simple: give it a brain (an AI model), give it memory (a place to store info), connect the right tools (like spreadsheets or messaging apps), and write a clear prompt that tells it what to do.

Sources

Lesson 3: Best practices and pitfalls

Start with workflows, not AI. Beginners often jump straight to building AI agents because they look cool, but that is a trap. You cannot build good agents if you do not understand how workflows for example, moving data between steps) actually function. That is like running before you can walk. Learn the fundamentals first, starting with JSON (a text format for data) and data types, because JSON is the language of almost everything you will touch in automation. It looks like code, but it is just pairs of keys and values, like a label and its content.

Also avoid the temptation to automate everything in sight. A key decision is amplify versus automate. Most people only think about making tasks automatic, but you should first ask what is worth pointing AI at. Sometimes you want to amplify a task or make it easier for a human, not replace the human entirely. Watch people who build automations just because they felt they should, and you will see wasted effort.

When you do create an automation, be specific. In a tool like Codex, you simply create a new automation, give it a title, and write a prompt. In that prompt, state exactly what you want the AI to do and choose where it works, such as locally on your machine. As your project grows, you can build on top of previous automations, which makes extending functionality even easier. Focus on foundations, choose your targets wisely, and write clear instructions — those three habits avoid the common pitfalls.

Sources