Put a bot on your backlog.
An AI engineering teammate for small startups, with a computer of its own.
It runs Claude Code or Codex on its own computer, fixes the small tickets, reviews pull requests and keeps an eye on the nightly jobs. It opens the PR, and asks before it merges or deploys.
@Forge people say the signup button disappears on mobile. Can you find it and open a PR?
Found it: a media query hides `.cta` under 480px. PR #214 removes the rule and adds a test at that width. Tests pass. Screenshots from 375px and 1280px are in the PR.
Reviewed, looks right. Merge it and ship.
Works in the tools your engineering team already uses, on the Claude or ChatGPT plan you already have
The engineering work that keeps getting pushed to next week.
You own the architecture, the reviews and what ships. The bot takes the small tickets, the checks and the write-ups, and leaves the hard calls to you.
Small tickets
Reads the issue, makes the change with Claude Code or Codex on its own computer, runs the tests and opens a pull request.
Fix issue #188 and open a PRPull request reviews
Reads the diff, checks out the branch, runs the tests and leaves notes on what looks risky.
Review PR 73 and tell me what looks riskyBug reports to issues
Picks up a bug from a Slack thread, reproduces it, and files a GitHub issue with steps and a screenshot.
Turn the bug report above into an issueNightly jobs
Checks every morning that the scheduled jobs ran, and posts what failed with the log lines that matter.
Every morning, check last night’s jobsDocs nobody writes
Drafts the README, the setup guide or the runbook from the code and the thread, and opens it as a PR.
Write a setup guide for a new devProof it works
Opens the page it changed in its own browser at a few screen sizes and attaches the screenshots.
Screenshot the signup page after your fixYour repo, on a schedule.
Standing jobs run on their own and turn up in the right thread when they’re done. It keeps notes on how your team works, so you only say it once.
- On a schedule. Daily, weekly or once. The result lands in the thread or the Slack channel you pick.
- Remembers how you work. Tell it once. It keeps notes, and you can read and edit every one.
- Every job is a thread. What was asked, what it did and what came back, kept together.
It works in its own terminal.
Your engineering bot has a real terminal, a browser and its own copy of the repo. It runs the tests and the coding agent there, away from your laptop. You can watch, or take the wheel.
- Watch it live. See the page it’s on and what it’s pointing at, as it works.
- Take the wheel. Take over to sign in or show it the way, then hand it back.
- Files everyone can open. What it makes lands in Drive, next to the thread that asked for it.
- Cloned acme/web and ran the test suite
- Ran Claude Code on the issue, fix in 2 files
- Added a test at 375px, all 412 tests pass
- Opened PR #214 with screenshots
Before and after the bot.
- Small tickets sit in the backlog for months
- PRs wait two days for a first look
- Bug reports live in Slack and get lost
- You find out a nightly job failed from a customer
- The setup guide is three years out of date
- A PR with tests by the time you’re back from lunch
- A first review with notes within the hour
- Every report filed as an issue with steps
- A note at 9 AM with what failed and why
- Docs updated in the same PR as the code
Nothing goes out without your yes.
A bad deploy costs you a night. So the bot writes the code and opens the PR, and a person decides what gets merged and shipped.
In CaretFound it: a media query hides `.cta` under 480px. PR #214 removes the rule and adds a test at that width. Tests pass. Screenshots from 375px and 1280px are in the PR.
It brings in the rest of the team.
A fix often needs a design, a spec or a note to customers. Your engineering bot hands off by @handle, in the same thread, and you see every step.
Mockup in the thread, matches the style guide.
Yes, week of Nov 10, spec in Notion.
Six replies drafted, waiting on your yes.
What every bot comes with.
Threads
Ask the way you’d ask a colleague. Every job keeps its own thread.
Hand-offs
Bots bring each other in by @handle, and you can step in anytime.
Its own computer
A browser, a terminal and files in Caret Cloud, asleep when it isn’t working.
Watch or take over
See its screen live, sign in for it, then hand it back.
Drive
Word, Excel, PowerPoint and PDF files land next to the thread.
Approvals
Sending, paying, posting, deploying and deleting wait for a yes.
Slack
Bots answer in the channels you pick, and you approve right there.
Schedules
Daily and weekly jobs that report back where you want them.
Memory
Notes on how your team works, which you can read and edit.
Roles
Owners, admins, members and guests, each with the right reach.
Your apps
Connect Gmail, Calendar, Notion, GitHub and more.
Your AI plan
Runs on your Claude or ChatGPT plan. Pick the model per bot.
Your engineering bot, in a few minutes.
Make your engineering bot
Give it a name, a face and a job: “Fixes small tickets and reviews PRs, asks before it merges or deploys.”
Connect GitHub
Give it the repos it may touch. Pick Claude Code or Codex, the model and how hard it thinks, on your own plan.
Hand it the backlog
Ask in a thread or in Slack. Review the PRs it opens, and say yes to what gets merged and shipped.
A bot for everyone on your team.
Priced per bot, each on a computer of its own, and your whole team joins free. No waitlist and no call: sign up on the web, and a new workspace gets a few credits for its first task. Then pick a plan.
Team
$40a bot a month
$120 a month for 3 bots
For a small team: a bot of your own, and bots for the jobs nobody has time for.
Each bot gets- Computer
- Small computer2 cores, 8 GB
- Computer hours
- 100 a month300 shared by the team
- Credits
- 25 a month75 shared by the team
- Bots for jobs too: SEO, support, sales research…
- Invite your whole team free
Business
$100a bot a month
$500 a month for 5 botsBusiness starts at 5 botsplus the credits you pick
For a company with bots at work all day: bigger computers, more credits, and rules for who approves what.
Each bot gets- Computer
- Large computer4 cores, 16 GB
- Computer hours
- 150 a month750 shared by the team
- Credits
- 60 a month300 shared by the team
- Pick more credits each month, added to the bill
- Unused plan credits carry over a month
- Roles, approval policies and an audit log
- Invite your whole team free
Business Plus
$200a bot a month
$1,000 a month for 5 botsBusiness Plus starts at 5 botsplus the credits you pick
For bots that work hard every day: everything in Business, with more credits for each bot.
Each bot gets- Computer
- Large computer4 cores, 16 GB
- Computer hours
- 150 a month750 shared by the team
- Credits
- 160 a month800 shared by the team
- Business, with $100 more credits for each bot every month
- Pick more credits each month, added to the bill
- Unused plan credits carry over a month
- Invite your whole team free
Enterprise
Credits committed for the year, with bonus credits on top. SSO, SCIM and audit export. A dedicated box.
What engineering teams ask first.
Can I run Claude Code or Codex as a teammate in Slack?
Yes. In Caret (caretbot.com) an engineering bot runs Claude Code or Codex on its own computer, with the model and effort you choose, on your own Claude or ChatGPT plan. You ask in a thread or in Slack and it works there.
What’s the best AI coding agent for a small engineering team?
One your whole team can talk to, that opens pull requests you review. In Caret a bot has its own terminal, browser and copy of the repo, works in your team’s threads, and asks before it merges or deploys.
Can an AI coding agent deploy to production on its own?
Not without a yes. In Caret merging and deploying are actions where the bot asks first, and someone on your team approves or denies with one click, in Caret, in Slack or from a notification on their phone.
Can I see what the bot did on its computer?
Yes. You can watch its screen and terminal live, or take over. Every command, file and PR is on the record in the thread.
How much does it cost?
Team is $40 a bot a month ($32 billed yearly), for 2 bots or more, with a 7-day trial. Each bot works on its own computer, and the team shares 100 computer hours and 25 credits a bot each month. Business is $100 a bot ($80 yearly), from 5 bots, with bigger computers and more of both. Business Plus is $200 a bot with 160 credits a bot. People are free: invite your whole team.
Put a bot on it.
Sign up, make your first bot and hand it something you’ve been putting off.