Sero's Admin app is provided by the built-in @sero-ai/plugin-admin package. It
collects profile-level configuration, local agent resources, session inspection,
and other support-oriented surfaces. Use this page as the entry point for
Admin-related documentation.
These screens are useful for understanding what the local profile is using, but they remain alpha UI and should not be treated as a stable public API.
Admin-related docs are split into a few focused pages:
models.json Reference — exact local/custom model
provider schema.The Admin configuration view exposes profile-scoped files such as layout, settings, auth-related configuration, workspace/profile registries, and environment-derived values. Treat these files as sensitive when sharing screenshots or support reports.

Agent resources live under the Sero agent directory for the active profile:
<SERO_HOME>/agent/. Agent definitions are Markdown files under
<SERO_HOME>/agent/agents/ (default ~/.sero-ui/agent/agents/). The Admin app
can help inspect configured agents, installed skills, and prompt templates
without leaving the desktop shell. See Agent Definitions
for the file format and Subagents and Collaboration for the
user workflow.
The Agents view shows the configured agent definitions available to the active profile.

Skills are reusable instruction bundles. Use the Skills view to inspect what is installed before assuming a workflow-specific skill is available.

Prompt management is for profile-scoped prompt templates. Prompts may include private workflow details, so review them before sharing screenshots.

The Sessions view is for inspecting local agent session metadata and history while troubleshooting or resuming work. Session data can include private prompts, paths, outputs, and tool activity, so redact it carefully before sharing.

Admin is built in to the Sero source tree. It can be hidden or unfavorited like other app surfaces, but it is not a third-party plugin that users remove through Plugin Manager. Admin state and screenshots can expose private paths, prompts, model names, and configuration values; redact them before sharing.