Vibe Admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Vibe Coding is text to code.
What about Vibe Admin: text to admin?
Think about it: how much of your day as a ServiceNow admin is spent navigating lists, setting filters, clicking through modules, just to answer a simple question or update a few records?
What if you could just ask in plain English (or your language) and get it done?
Here's how we made this work for ServiceNow:
1. Everything in ServiceNow is a table.
2. Move the database from behind to the front of the ServiceNow API -> now you can query against the GraphQL/REST Table API, respecting business rules, ACLs, etc., using standard SQL (ANSI '92) for full CRUD operations.
3. Connect that SQL layer to Claude Code (the best Vibe Coding tool for me right now).
4. Ask Claude for anything and let it write and execute SQL to administer your instance. Start with a PDI as you'll want to experiment freely.
That's how this free VS Code agent works: Pocket Admin
It was originally built to shield ServiceNow developers from the complexity of managing their PDIs by putting Vibe Admin in the Vibe Coding loop so they could focus on building, not administrating.
If you're an admin, I think it's worth a look. And please, don't hold back. Be as brutal as you want with your feedback.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Or just create favorites and only have one click to reach what you need. That limits the annoying hallucinations.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Great point about hallucinations, it's a fair concern. But Claude Code isn't a black box. It reasons out loud: you can see every SQL statement it writes and executes in real time, so you have full visibility at every step. When it makes a mistake (and it does), you can watch it investigate the data model, correct itself, and move on. Nothing happens that you can't see or review.
But here's where it gets interesting. The real value of an admin isn't clicking through favorites, it's the knowledge behind what those favorites point to. Creating reports, designing workflows, configuring business rules. That's where expertise matters.
So I recorded a live session. One prompt:
"Create a stacked bar chart report on the incident table showing active incidents grouped by priority and stacked by state. Include data labels, legend, and set the title to 'Incidents by Priority & State' with subtitle 'Active incidents analysis'. Then pin it as a blue favorite in my navigation bar so I can access it with one click."
Two minutes later, Claude had built the full stacked bar report, with the right filter, grouping, labels, legend, and pinned it as a blue favorite. One click access included.
The session (animated gif) is uncut and unedited, so yes, two minutes of watching an AI think and write SQL isn't exactly thrilling. But that's the point: it's real, not a polished demo. You can see exactly how it works, including when it stumbles and recovers.
And of course, as with anything AI generates, the admin should review before shipping to production. That's just good practice regardless of the tool.
