AIVA for Developers

Ship withoutlosing the thread.

Issues, PRs, Slack threads, local files, and the release that’s due Friday — context lives everywhere. AIVA pulls it together: tracking assigned work, summarizing reviews, watching notifications, and keeping your release prep on rails.

What AIVA does for you

Context, gathered. Shipping, unblocked.

Track your GitHub work

Assigned issues become tasks, PRs waiting on your review get summarized, and AIVA can tell you exactly what’s blocking a merge.

Stay on top of Slack

AIVA reads the channels and threads you care about, catches the @-mentions, and drafts replies with full thread context.

Work with local files

AIVA keeps drafts, snippets, exports, and research in its on-device file cabinet, linked to the task they belong to.

Run release prep

Changelogs, checklists, the “did we update the docs?” loop — AIVA tracks the steps and reminds you before the cutoff.

Why it matters

What changes when AIVA has your back.

Context, gathered for you

Assigned issues become tasks, PRs waiting on your review get summarized, and AIVA can tell you exactly what’s blocking a merge — across GitHub, Slack, and your local files.

  • Review queue summarized with what’s failing
  • Assigned work tracked automatically
  • Slack threads caught up, @-mentions flagged

Working

  • Scanned inbox & calendar
  • Flagged what needs you
  • Drafted the follow-ups

Release prep on rails

Turn your release checklist into a recurring loop. AIVA tracks the steps — docs, changelog, sign-offs — and surfaces them before the cutoff so nothing blocks the ship.

  • Checklist resurfaced on schedule
  • Changelog and sign-offs tracked
  • Fewer last-minute fire drills

Loop

Every weekday · 8:00 AM

Morning brief — next run in 14h

Safe by default

Read-only work happens silently, but anything that changes the world — creating issues, posting, editing files — asks first. Shell and destructive git actions always prompt; there’s no silent “allow always”.

  • Reads and summaries run silently
  • Writes and posts ask first
  • Destructive commands always confirm

Approval needed

AIVA drafted a reply to the investor. Send it?

ApproveEditDecline

Example prompts

Try saying

What issues are assigned to me and what’s overdue?

Summarize the PRs waiting on my review and what’s failing.

Catch me up on #eng since this morning.

What’s blocking PR #482 from merging?

Remind me of the release checklist every Thursday.

Save this snippet and link it to the release task.

What it stays on top of

Nothing slips.

Issues & PRs

Assigned work tracked; reviews summarized.

Notifications

GitHub alerts that matter, surfaced.

Slack threads

Caught up, with @-mentions flagged.

Local files

Snippets and drafts, organized.

Release prep

Checklist and changelog, on schedule.

Permission model

You stay in control of every consequential action.

Read-only work happens silently. Anything that changes the world waits for your approval — and destructive actions always ask prominently.

Safe — does silently

  • List repos, read issues, PRs, and notifications
  • Read Slack and files
  • Track tasks

Asks first

  • Create a GitHub issue
  • Post to Slack
  • Edit files in coding mode

Always asks

  • Shell commands (rm, git reset --hard, force pushes)
  • Bulk deletes

Common workflows

A day with AIVA.

01

Review queue brief

A loop summarizing PRs awaiting your review — what changed, what’s failing, what’s blocking — so review time isn’t archaeology.

02

Assigned-work radar

New issues assigned to you become tracked tasks with a heads-up, so nothing rots in your notifications.

03

Release runway

AIVA keeps the release checklist and reminds you of each step before the cutoff — docs, changelog, sign-offs.

Without your approval, AIVA won’t

No surprises.

These never happen on their own. AIVA drafts and asks; you decide.

  • Create issues or post to Slack
  • Edit files in coding mode
  • Run shell commands or destructive git operations (always asks prominently)

Local-first notes

Your data, on your machine.

AIVA runs locally on 127.0.0.1; in Local mode your code, files, and keys stay on your Mac.

GitHub and Slack access is OAuth-based, encrypted locally, and revocable any time.

Shell and destructive git actions always ask first — there’s no silent “allow always”.

Works across your apps

The tools that power this.

Connected app

AIVA for GitHub

AIVA reads your issues, pull requests, and notifications, turns assigned work into tracked tasks, and files new issues on request — creating only after you approve.

Built-in app

AIVA for Local Files

AIVA keeps its own file cabinet on your Mac — drafts, exports, research reports, received attachments, generated artifacts — so the work it produces is organized and findable instead of lost in chat.

Connected app

AIVA for Slack

AIVA reads the channels you point it at, summarizes what you missed with full thread context, and posts on your behalf — but only after you approve the exact message.

Built-in app

AIVA for Loops

Loops are AIVA’s recurring schedules — morning briefs, weekly wrap-ups, periodic checks. Describe them in plain language; AIVA handles the cron, the timezone, and what to do when your Mac was asleep.

Built-in app

AIVA for Calendar

Beyond your Google Calendar, AIVA keeps its own event timeline — the things it’s tracking on your behalf — with categories, statuses, notifications, and links to the contacts and tasks each event belongs to.

Get started

Ready when you are.

Create your account on the web — it carries straight into the Mac app.