Agent Lifecycle
Draft vs Published Agents in KriyaOS
This guide explains one of the most important ideas in KriyaOS: the difference between a draft agent and a published agent.
If this feels confusing at first, that is normal. Once you understand this difference, the rest of the agent workflow becomes much easier to follow.
Simple Rule
Think of draft as the version you are still shaping, and published as the version you are comfortable treating as live.
What A Draft Means
A draft is the version of your agent that you are still working on.
In plain language, a draft is your in-progress version.
You use a draft when you want to:
- keep editing the agent
- test changes before they go live
- improve prompts, knowledge, or settings
- take your time before sharing the agent with other people
What A Published Agent Means
A published agent is the live version.
This is the version you are treating as ready to use.
In plain language, published means:
- this is the version you want other people to interact with
- this is the version you want to share or connect later
- this is no longer just your working copy
Why The Difference Matters
The difference matters because you do not always want your latest edit to become the live version immediately.
Keeping drafts and published versions separate helps you:
- test safely
- make changes without rushing
- avoid showing unfinished behavior to users
- improve an agent over time with more confidence
Which Version People Use
The most helpful way to think about it is:
- Draft is for you while you are working
- Published is for the live version you are ready to use
This means the version you are editing is not automatically the same as the version that is considered live.
How This Shows Up In KriyaOS
After you create an agent, you may move between:
- the editor, where you change the draft
- the playground, where you test the current draft
- the published view, where you see the live version
These are related, but they are not all showing you the same state in the same way.
When A Draft Is Normal
It is normal to keep an agent as a draft when you are:
- still writing or improving instructions
- adding knowledge
- checking whether responses feel right
- deciding if the agent is ready for real use
Keeping something in draft does not mean you are doing it wrong. It usually means you are being careful.
When Publishing Makes Sense
Publishing makes sense when:
- the agent gives answers you are comfortable with
- the prompt and behavior feel stable
- any important knowledge is ready
- you are ready for the live version to represent your work or business
Common Misunderstandings
- A draft is not the same as a live agent.
- Creating an agent does not always mean it is immediately published.
- If you change a draft later, that does not automatically mean the published version has changed too.
- If uploaded knowledge is still processing, the agent may not behave as expected yet.
Business Agent vs Custom Agent
The two creation paths handle this differently:
- Custom Agent creates a draft first
- Business Agent creates and publishes during the guided flow
That is why some users see the draft workflow more directly than others.
Before You Publish
Before you publish, it helps to check:
- whether the agent answers in the tone you want
- whether important instructions are complete
- whether connected knowledge is ready
- whether you are comfortable treating this as the live version
Next Step
If you are ready to move from draft to live, read How to Publish an Agent.