How To Build a Personal Agentic Operating System

What It Covers

Nufar Gaspar introduces AgentOS, a free platform-neutral training program for building a seven-layer personal agentic operating system. The framework covers identity, context, skills, memory, connections, verification, and automations — designed so knowledge workers can run any AI tool on a shared, portable foundation.

Key Questions Answered

• •Identity Layer First: Every agentic tool reads one file before anything else — your identity file (called soul, agents.md, or .claude depending on the tool). Rather than writing it from scratch, prompt any AI to ask you 15 questions about your work style, preferences, and non-negotiables, then draft from your spoken answers. Ship a 70% version and patch it over three weeks.
• •Context Curation as Practice: Three to five single-page, dated context files — covering team structure, quarterly priorities, stakeholders, and operating principles — outperform any lengthy document. Every time you catch yourself re-explaining your situation to an AI, that explanation belongs in a context file. No model improvement will ever know your roadmap unless you write it down.
• •Skills as Reusable Instruction Sets: Knowledge workers typically have 20 to 30 repeatable workflows — meeting prerads, daily briefs, stakeholder emails, commitment trackers. Each skill is written once as a trigger-process-output instruction. A first-version skill used for one week, then patched based on observed gaps, produces better drafts than restarting from zero every session.
• •Connections: Read Before Write: When connecting agents to live systems like email, calendar, Slack, or Jira, start with read-only access and observe agent behavior for several weeks before granting write permissions. Agents with loose permissions on company Slack have already caused real incidents — sharing private notes and draft feedback with unintended recipients — making least-privilege access a concrete security requirement.
• •Compounding Agent Costs: The first agent built on an AgentOS — such as a chief-of-staff agent handling inbox review, meeting prep, and commitment tracking — may take a full weekend to build. Each subsequent specialist agent (research, board prep, content) takes only an afternoon because it inherits the full OS foundation, making every additional agent progressively faster and cheaper to deploy.