VisiCore AI — Extending X10
Vizzy + The AI Brain

Vizzy

Vizzy is a master consultant on call 24/7: an agent that reads The AI Brain, composes the platform CLIs, and records its work to ConnectWise.

Customer pain

Enterprises pay for senior Splunk and Cribl experts, and those experts are scarce. No one is free at 2 a.m. on a Sunday, and time costs a lot at 2 p.m. on a Tuesday. A question that arrives after hours either waits for morning or goes to whoever is awake — rarely the right person.

Vizzy closes that gap. It is a master consultant — it carries the experience of every job VisiCore delivers, which no single engineer can. The Sunday 2 a.m. question gets a master-level answer.

What Vizzy is

Vizzy is the AI agent harness inside X10. A harness is the software that runs the agent. It runs a reasoning loop: it reads The AI Brain, writes the platform CLI commands, and tells you each action as it takes it. Finished work goes to ConnectWise, so the ticket — not the chat log — is the lasting record.

A harness, not a chatbot

Vizzy wraps the CLIs that talk to the Cribl and Splunk APIs. It writes commands, runs them through a dry run — a safe preview — and reports what it does as it does it.

Always on

An expert answer is there at any hour. No waiting for a consultant to come online.

SaaS-simple

No local setup and no library upkeep. The CLIs are for people who want to tinker. Vizzy is for people who want it to just work.

Records its work

Every completed action lands in ConnectWise as a ticket, linked to billable time.

One unit of work: a task enters Vizzy, which combines knowledge-base context and client credentials, composes a CLI dry run, waits for engineer approval, executes through the vendor API, and records results

The precision split

Vizzy is AI. The commands it writes are not. Keeping the two apart is the whole safety model.

Vizzy is the AI

The harness reasons, plans, and drafts. It decides what to try and explains why.

The CLIs are rule-based

The commands Vizzy writes run through the platform CLIs, which call the Cribl and Splunk APIs directly. The same command gives the same result every time — no model in that path.

The engineer approves

Every change gets a dry-run preview and a senior engineer's approval before it touches a customer environment. The review is a feature, not a cost to cut.

Vizzy drafts at master-consultant level. A person still confirms every draft before it runs.

Surfaces

Everything sits behind one shared API. So each new chat surface adds on. It is not a rebuild.

X10 web — live

Vizzy runs in the X10 portal today for internal tenants. Light and dark modes, works on mobile, and sessions that hold across page loads.

Slack — in progress

A Slack surface is in active development. It brings Vizzy to where the customer's engineers already work.

Teams — planned

Microsoft Teams brings the same interface to the enterprise. Email-to-ticket already works.

Human handoff — planned

When Vizzy hits the edge of what it can do, it hands off to an available consultant. That person picks up the session and keeps going. The work is billed and documented through ConnectWise on its own.

One agent, many surfaces: X10 web (live), Slack (in progress), Teams and human handoff (planned) all front a common API interface into Vizzy

How a request flows

A question arrives

From X10, and soon from Slack or Teams — at any hour.

Vizzy reads The AI Brain

It pulls VisiCore's best practices for that client environment before it drafts a thing. See The AI Brain.

Vizzy writes CLI commands

The platform CLIs do the real work against the Cribl and Splunk APIs.

An engineer approves the dry run

Nothing touches a customer environment until a person signs off on the preview.

The work is recorded

Finished actions land in ConnectWise, linked to billable time.

Why credentials stay safe

  • Client connections live in ConnectWise, which holds SOC 2 Type 2 certification. Credentials never touch a filesystem.
  • The harness hands the agent a ready-authenticated client object, so the model never sees a raw password.
  • Isolation lives in the harness, not the agent. One client can never reach another's environment.

Next

On this page