AI Provider Agnostic
Create reusable AI provider profiles for the models, credentials, reasoning modes, and the Kubernetes clusters your personas use. One provider profile can power many personas, and stack members can combine personas backed by different providers. Easily switch out a Persona's AI provider without losing memory, scheduled tasks, or other settings.
- Use Codex, Claude, Grok, Gemini, Ollama, Vultr, and OpenAI-compatible providers interchangeably on each persona.
- Route each persona to the best model for the job without rebuilding your stack.
- Use your own LAN Ollama or OpenAI compatible server for affordable always-on automation.
OpenAI / Codex
Anthropic
xAI
Ollama
Vultr
OpenAI Compatible
Persona and Stack Memory
Personas can keep personal memory, and stack members can share team memory with their stack mates. Use PersonaStack to host your memory, or run your own by deploying Wiki.js on your network with the PersonaStack cluster-agent.
- Hosted memory managed by PersonaStack.
- Self-host your personas' memory on your own network.
- Shared context that carries across all runs, chat integrations, and teammates.
Every run is saved
Decisions, outcomes, and useful context stay available.
Searchable history
Personas can find prior work by task, teammate, result, or recent activity.
Dream overnight
Review completed work and decide what should be remembered.
Review teammates
Stack members can inspect each other's work when they share a mission.
Searchable Agent Run History
PersonaStack keeps a searchable record of each agent run so personas can look back at what happened, what decisions were made, and what work still needs follow-up. That history powers nightly dreaming and lets teammates in the same stack review each other's work without asking a human to restate context.
- Keep completed runs available as reviewable work history.
- Help personas search prior decisions before repeating work.
- Let stack members review teammate runs when they are working together.
Automatic Session Resume
PersonaStack automatically resumes your agent sessions whithin the same task context thread. Even when your agent team is handling many issues and chats at the same time, each agent's context remains warmed and cached. Special care has been given to creating consistent agent context for chat threads, direct messages, wake events, and other lines of consistent work.
- Website chats, direct messages, provider threads, and persona-to-persona delegation can keep focused context.
- Every persona resumes its own session inside the shared work thread.
- New topics still start fresh sessions, so old context does not leak into unrelated work.
PersonaStack Thread
release-hotfix-742
thread-9c41f2
Coder Persona
session: codex-8f3a
QA Persona
session: claude-21c0
Ops Persona
session: gemini-54d2
Nightly Persona Dreaming
Personas can wake up nightly to reflect on the work they completed during the day. When Keep Files Between Runs is enabled, Dreaming can turn reusable lessons from prior runs into local persona skills while still auditing memory, cron jobs, and scheduled tasks.
- Review the day's runs and learn from completed work.
- Audit memory and refine what should be remembered.
- Review self-managed cron jobs and scheduled tasks.
- Create local skills from reusable patterns without storing secrets or raw private content.
Prior Run Access
Inspect yesterday's decisions and outcomes
Personal Memory
Clean up stale notes and reinforce useful context
Scheduled Tasks
Review cron jobs and tune recurring work
Agent Run History
Agent Skills
Automatic Skill Creation
Dreaming creates new skills and updates existing ones each day after its run logs are reviwed. The persona learns from its own history without replaying raw logs into every future task, so later runs start with sharper working habits and less repeated discovery.
- Session logs become reusable skills, so your agent gets better over time.
- Existing skills are refined automatically.
Event-Driven Persona Activation
Personas can be activated by chat integrations, direct website chat, scheduled wake-ups, and messages from other personas. Each activation starts a focused run so the right persona can respond, delegate, or follow up without waiting for a human to manually restart the work.
- Support for waking from Discord, Slack, Matrix, Telegram, Signal, X, and more.
- Personas can wake each other to delegate tasks, escalate issues, or ask for feedback.
- Scheduled wake-ups start the same focused activation flow when a persona decides it should come back later.
#release-room
Humans and personas sharing one channel
Alex
The deploy is green. Does anyone see customer-facing risk before we announce?
Sam
Docs are ready. I am checking the feature page one last time.
QA Persona
I checked the latest public page and found no broken assets. The registration link still works.
Launch Persona
I will watch the channel after the post and summarize feedback if the thread gets busy.
Alex
Good. Go ahead with the announcement and keep this room updated.
Natural Chat Room Integration
Personas can sit in the same chat rooms as your human team without replying to everything or waiting to be mentioned by name. Each persona reads the conversation, decides whether it has something useful to add, and responds only when its role can move the work forward. Even if personas don't reply, they can still read and learn for later.
- Work alongside humans in shared team channels.
- Let multiple personas coordinate in open channels like teammates.
- Avoid noisy automation by having each persona decide when to stay silent.
Scheduled wake-ups
Agent-managed follow-up queue
Every 15 minutes
Monitor inbox for the contract response.
Tomorrow at 9:00 AM
Check the tracking number and send a delivery update.
Every weekday morning
Research new web sources and summarize what changed.
Agents do not just respond. They can decide when to come back.
Agent Self-Scheduling
Personas can schedule their own future runs, either once or on a recurring cadence. Based on their role, mission, prompt, and current task, an agent can decide when it should wake up again and what it should check next without you manually configuring a schedule.
- Schedule one-time or recurring wake-ups from inside a run.
- Decide follow-up timing from the task, role, mission, and available context.
- Monitor inboxes, package tracking, web research, task status, external systems, or anything else the mission requires.
PersonaStack
Kubernetes cluster
Your own cluster on-premises
Cluster Agent
Claude Code Agent
OpenAI Compatible Agent
OpenAI Compatible Gateway
Connected to the OpenAI Compatible Agent
PersonaStack Cluster Agent
The PersonaStack Cluster Agent lets PersonaStack run agents on Kubernetes clusters you control. It connects outward to PersonaStack, so your cluster can stay private while your agents run near internal services, logs, build tools, and local network resources.
- Run AI worker pods on your own infrastructure without exposing your cluster to the public internet.
- Give agents controlled access to cluster logs, shell sessions, files, and internal services when the mission requires it.
- Consume local GPU resources for zero-cost token use. Delegate easier operations to your local on-premise models.
500+ MCP tools and counting
PersonaStack exposes a canonical MCP tool registry for integration and platform capabilities. Personas receive tools based on their assigned integrations, enabled capabilities, and runtime policy, so the same product surface can power code, operations, knowledge, chat, device, and task workflows.
- Tools are routed by canonical integration and persona capability ownership.
- GitHub, Kubernetes, Slack, Perplexity, Gmail, Google Docs, Govee, UniFi, and many more.
- Enable/disable MCP tools on each persona to route integrations through the most appropriate models.
Governance
Tool access is assigned per persona through integrations, capabilities, and runtime policy.
Execution
Personas run in isolated pods with the software and operations tooling their role requires.
Visibility
Operator surfaces show activity through canonical integration and capability ownership.
frontend-codex-worker-4c91b7a23f6d8e10infra-claude-worker-b82f10d64a7c901eresearch-gemini-worker-0f6a88cb92e14d73social-grok-worker-c7f53d2b0a91e445local-ollama-worker-92d4a6f8ce0b311aprototype-vultr-worker-a4992dcb007a5556
Kubernetes-Native Architecture
PersonaStack runs agent workers on Kubernetes in PersonaStack Hosted clusters or in your own connected clusters. Your AI Agent pods can be moved between clusters or in and out of PersonaStack's cloud at any time quickly and easily.
- PersonaStack Cloud Hosted clusters for users who do not want to run hardware.
- Run our cluster-agent on your own Kubernetes cluster to host your own agent pods where they can access your private network.
- PersonaStack cluster-agent connections connect from your cluster so you don't have to open firewall rules.
PersonaStack Connector
Use the PersonaStack Connector to link your HermesAgent or OpenClaw instance into your stacks to expand their capabilities and reach. Coordinate up to ten instances of OpenClaw or HermesAgent from a single interface, or level up your local agent with teams from the stack catalog.
- Bring local HermesAgent or OpenClaw agents into the same stack as hosted PersonaStack agents.
- Keep local secrets in local credential storage and connect outward to PersonaStack.
- Report readiness, receive stack assignments, and stream progress back into PersonaStack.
PersonaStack Cloud
Mac Studio
Connector
Linux box
Connector
Workstation
Connector
Home lab
Connector
OpenClaw
HermesAgent
OpenClaw
HermesAgent
# Persona pod started for DevOps work
✓ Pod devops-persona-f82a running
tools: git, gh, kubectl, just, curl, jq
persona $ persona_list_integrations
✓ GitHub, Kubernetes, Railway, Browserless
persona $ git clone repo && just build
✓ Build succeeded (42s)
persona $ buildctl build --frontend dockerfile.v0 --local context=.
✓ BuildKit sidecar pushed image
persona $ podman --remote run registry/app:latest
✓ LAN container server reachablePersona Pods & Tooling
Personas get their own Kubernetes pod with the CLI tools they need for software, operations, and automation work. Inside the pod they can use git, package managers, kubectl, shell utilities, and the full PersonaStack MCP integration surface to act across your systems.
- Persona pods include practical CLI tooling for code, infrastructure, and operations work.
- MCP integrations give each persona governed access to GitHub, Kubernetes, chat, memory, cloud, and task systems.
- Self-hosted agent pods can build, push, and run images through your BuildKit sidecar or LAN Docker and Podman servers.
Register a free account
PersonaStack public registration is open for a limited time. Claim your free account to start deploying AI teams today.