Skip to main content

VIGIL

Sandboxed overnight assistant executing pre-authorized OAuth workflows over Web and Telegram with per-action audit tables and one-click revocation.
Autonomous Agents
Active Security Pattern
CATEGORY
Autonomous Agents
STACK
Next.js · Prisma · Composio OAuth
STATUS
Active Security Pattern
Execution Surface
Local Shell Risk
Credential Scope
Raw API Keys
Night-Shift Trace
Opaque Output
Kill Switch
Manual Clean-up
Recurring Jobs
Fragile Scripts
Tool Connections
Ad hoc Wrappers
Vector Memory
Ephemeral
Remote Reach
Terminal Only
Execution Surface
Remote Sandbox
Credential Scope
Scoped OAuth
Night-Shift Trace
Line-Item Log
Kill Switch
1-Click Revoke
Recurring Jobs
Queued Watch
Tool Connections
Composio OAuth
Vector Memory
PostgreSQL Store
Remote Reach
Web + Telegram
MEDIA FORMAT NOTE

Promotional presentation: dark motion piece depicting Vigil's isolated sandbox, audit log, and instant revocation model (not a live client server feed).

Attribution: Joaquin Villarreal · Sandboxed Night-Shift Agent Architecture.

Overview & Problem Addressed

Vigil is a TypeScript and Next.js background agent built around clear boundaries: zero direct host-laptop execution, OAuth-scoped tool access, isolated sandbox runs, and a readable audit row for every step taken.

Capabilities & Workflow Execution

Giving a background task raw filesystem or key access on a primary executive workstation carries avoidable risk. Vigil runs scheduled tool checks inside an isolated sandbox, stores vector memory in PostgreSQL via Prisma, sends morning digests to Web or Telegram, and revokes tokens in one click.

Executive Assistant Support & Application

Applies least-privilege controls to overnight monitoring: preparing morning status updates, checking public vendor feeds, and printing a clear verification table at start of day so nothing executes off the record.

Configured Implementation

Next.js frontend and API routes, Prisma PostgreSQL adapter, Vercel AI SDK, `@composio/core` OAuth connectors, CLI runner, and Telegram delivery handlers.

Operational State & Availability

Active implementation used for least-privilege sandbox workflows. Environment secrets and OAuth tokens stay isolated and private.

AVAILABILITY & DIRECT CONTACT

Want to discuss this project or set up a similar workflow? Write to jevillarreal170@gmail.com and I will gladly share what can be shown.

Public repository links stay unpublished while private configs, credentials, and environment records remain offline. No confidential company data or invented dates appear here.