For IT and security

Skills and local tools, ready for your review

VibeExec combines human-readable Agent Skills with Python helpers for setup, updates and a local cockpit. The cockpit uses HTML, CSS and JavaScript to display local drafts, briefs and notes. The installed tools do not upload working content to VibeExec. Our website separately handles sign-in, package access, support requests and website analytics

What gets installed
Skills and local tools
Content sent to VibeExec
None by the skills
Connector scope needed
Read access by default
Initial knowledge build
Allow a weekend
What it does

Runs inside the AI platform you already administer, under the agreement you already have

Reads mail and documents through connectors you control, scoped to what the user can already see

Writes its output as files on the executive's managed laptop, under your existing endpoint policy

Includes readable Markdown skills, Python helpers, local HTML/CSS/JavaScript interfaces, and launcher and integration scripts for review

What it does not do

Never sends mail. Replies are local files by default; creating unsent mailbox drafts requires an explicit user request and a connector with write access

Does not send working content to VibeExec. Your approved AI provider and connectors process content under their terms and your settings

Does not install a separate VibeExec background service; your selected AI tools still need their usual network access

Does not collect mailbox credentials or document contents. Website account and usage records are covered in our security and privacy page

Provisioning
01

Enable skills for the group

Turn on the skills capability for the executives who need it. You can scope by group rather than tenant-wide

Admin console
02

Assign the seats

Claude Code, Cowork, Codex or ChatGPT Work for the same group. Confirm availability and licensing under your company’s agreement

Licensing
03

Approve the connectors

Email, and if in scope SharePoint or Drive. Read access is sufficient for the default workflow. Optional mailbox drafts need a separately approved write-capable connector

Connectors
04

Read the package

Review the skills, executable helpers, local interfaces, launcher scripts and integration settings under your software approval process

Security review
05

Push it to the group

Distribute the reviewed package through your approved channel, then complete setup in the selected AI app

Deployment

Local access and updates

Setup writes the executive’s workspace and personal AI skills folders. Python helpers run on the laptop; the dashboard and cockpit are served on the loopback address (127.0.0.1). The cockpit can read workspace files, save edits to notes and open the mail app. It is not a hosted copy of the executive’s workspace. AI apps and connectors still need their own approved network access and permissions.

Updates run when the executive asks. HTTPS requests to www.vibeexec.co use /api/update to check a version and /api/update/download to retrieve the release ZIP. They send an installation licence; the check also sends the installed version. New updaters use an Authorization header; older installations send the licence in a URL parameter. Treat both as credentials and redact them from diagnostic reports. Our service records update checks and account/version information, not workspace content.

The updater checks the archive’s SHA-256 checksum before replacing vendor files and preserves personal material and locally edited files. This is an integrity check against our server’s release metadata, not an independently signed release. If your gateway blocks a download, review its policy event before approving the endpoint or package. No security control needs to be disabled to troubleshoot it.

Want to know more, or read it line by line?

Write to us and we will send the full package for review, answer your security questions, or walk your team through it. No sales call

Contact us
Security and privacy, in plain English