Triggered by schedules and events
Orpius can run work at defined times or react instantly to signals such as webhooks, system events, or internal follow-up events. Each trigger becomes a managed activity with supervision and logging.
Live example
Autonomy in the real world
Silverfix is a site that publishes without human involvement. An Orpius agent periodically researches current topics, writes a post, publishes it, and then sends you a sharable link. It is a practical demonstration of what autonomous work means inside Orpius.
Orpius can run multistep work reliably over time, driven by schedules or events, with the tools and guardrails you define.
What the agent does
Silverfix is produced by a scheduled Orpius activity that runs unattended.
- Runs on a schedule (and can also run from events)
- Researches topics using web search and web retrieval tools
- Writes a new markdown post with consistent front-matter
- Publishes by pushing to a GitHub repo using a secret token
- Sends a notification with a share-ready link
- Uses memory to avoid repeating topics
How Orpius stays autonomous
Agents do not just respond. They plan, use tools, persist state, and keep going.
Tool-driven execution
The agent operates in a structured model-and-tools loop: it can search, retrieve pages, write files, call APIs, run code in a sandbox, and combine tools as needed to finish the job.
Secrets stay private
Sensitive values (tokens, keys, passwords) are stored as Secrets and referenced by name. The model receives references, and Orpius injects the real value only at tool-execution time.
State and memory
Agents can track what happened last time, what has already been published, and what should be avoided or repeated. This is how autonomous work improves, not just repeats.
Publishing as an action
Publishing is just another outcome: write content, push to a repo, trigger a build, update a site, notify people. Orpius treats those as real operations, not a manual checklist.
Verification and audit trail
Activities are tracked, supervised, and can be verified after execution. This makes autonomy observable and controllable, rather than mysterious.
Want to copy this pattern?
The Silverfix example uses a simple recipe: a scheduled activity, web research, safe secrets, publishing, and notification. The same pattern applies to operational work: reconciliations, monitoring, reporting, triage, and follow-ups.