Skip to main content

The CarsXE team's AI teammate

Your work.
A little lighter.

Allen links GitHub, ClickUp and your AI models, so reviews, ticket status and follow-ups keep moving without anyone chasing them. Then it tells you, in plain English, what it did and why.

Example requests. Ask in chat, or mention Allen in GitHub and ClickUp.
Download the app

Sign in with a verified @carsxe.com Google account or an approved testing account.

Today+0−0
This morningexample · sample data
listening for GitHub and ClickUp events

An example morning. This is how the console shows Allen’s work: running, done, failed and waiting on you.

meets people in the tools they already use

  • GitHub
  • ClickUp
  • Linear
  • OpenRouter
  • Cursor
  • Cloudflare
  • Upstash
  • WhatsApp

one line, two readers

Every action, legible to whoever reads it.

A PM reads what Allen did today in plain English. A developer reads the same lines with IDs, durations and the exact call. Nobody has to translate a bot log for anyone else.

Choose a reader
CX-1290 · Checkout retries
Since 9:00example
1Done:
The checkout retry fix was reviewed. The summary is on the pull request.
2Done:
CX-1290 now shows that the fix is merged.
3Needs you:
Allen wants to move CX-1290 to Ready for QA. It’s waiting for you.
4Failed:
Release notes are late because GitHub didn’t answer. Allen tries again at 2:00 PM.

what allen does

The follow-up work, handled the CarsXE way.

Allen follows the team’s own workflow and review style, not a generic reviewer’s. Developers stay in GitHub, PMs stay in ClickUp, and both sides stay current.

branchesrest

Pull request reviews and summaries

Allen reviews pull requests against CarsXE’s conventions and writes a summary a PM can read.

src/webhooks/checkout.ts+24−6
−await sendWebhook(event)+await withRetry(() => sendWebhook(event), { attempts: 3 })
a

Summary for the PM: failed checkout webhooks now retry up to three times before they’re reported, so fewer orders get stuck.

relayrest

ClickUp stays in sync

When a pull request merges, the linked ticket says so. Nobody asks “is this live yet?”

CX-1290in reviewmerged
pigeonholesrest

Comments that matter, forwarded

Important GitHub comments reach the person who needs to answer them, wherever they work.

pr#482 · review comment

“Can we keep the old endpoint until the mobile app updates?”

forwarded to the ticket owner

formatrest

QA checklists and release notes

Checklists drafted from the PR and the ticket. Release notes written from what actually merged.

  • DoneRetry fires after a 502 from the gateway
  • DoneOrder status updates after a retried success
  • RunningAlert after the third failed attempt
slowrest

Scheduled jobs you can read

Recurring work runs on a schedule written in words, with every run and its result on record.

0 9 * * 1-5Weekdays at 9:00 AM
settlerest

Agents, skills and workflows

Admins build specialized agents, teach skills and draw workflow graphs for the team’s own jobs.

merged
summarize
notify

how allen works

How Allen works

Developers stay in GitHub. PMs stay in ClickUp. Allen keeps both sides current, and says what it did, what it plans next, and why.

  1. 01 github · clickup · chat
    routerrest

    Work arrives

    A mention, a status change, a review request, a merge. Allen picks up GitHub and ClickUp events as they happen.

    Idle
  2. 02 agent run
    stackrest

    Allen plans

    It reads the pull request, the ticket and the team’s memory, then lays out what it intends to do.

    Running
  3. 03 approval
    padlockrest

    You approve what matters

    Actions that change something can wait for a yes. The request comes with its reason attached.

    Needs you
  4. 04 interaction
    terminalrest

    Done, and explained

    The result lands where people already look, with a plain-language note on what changed.

    Done

approvals

It asks before it acts.

Running, waiting for you, failed and done always look different, so you never have to guess what state something is in. When Allen needs a decision, the reason comes with it.

  • Actions that change something can wait for your approval.
  • Each request says what Allen will do and why.
  • Every decision is recorded next to the run, for anyone to check later.
Approval requestNeeds you

Move CX-1290 to Ready for QA?

Why
PR #482 merged to main at 13:42 and its checks passed. The QA checklist is attached to the ticket.
Action
clickup.update_status(CX-1290, "ready for qa")
Asked by
PR merge workflow
try it · example

download

In your browser, on your desk, in your pocket.

The browser needs nothing installed. The apps keep Allen a click away, and desktop update notices arrive through your operating system while Allen is running.

desktoprest
androidrest

  • Windows

    Windows 10 and later · x64 installer

    loading…

  • Mac

    Apple silicon · M1 and later

    loading…

  • Mac with Intel

    Intel processor · x64 installer

    loading…

  • Android

    Install the APK on your phone

    loading…
Release notesAndroid downloads install directly from GitHub.

access, costs and privacy

An internal CarsXE workspace.

lockersrest

Who can sign inAccess requires a verified @carsxe.com Google account or an approved testing account. Ask your workspace administrator about access, usage costs, and the applicable terms and privacy policies before signing in.

What connecting meansGoogle sign-in identifies your account. Connecting work tools is a separate step; only administrators can authorize workspace connections. You can skip that step during setup.

Let Allen take the follow-up.

Nobody chases a status update. Nobody misses an important comment. And everything Allen does is written down where you can read it.