For developers

Pebrik Code

Coding agents that work on your own computer, inside your company's rules. Describe a change, and Pebrik Code plans it, builds it in its own branch and sandbox, and hands it to you to review.

Ask about Pebrik Code About Pebrik
One task

From a sentence to a commit you approve.

  1. 1

    Describe the change

    Pick a project and say what you want. Choose the model, effort and spending limit, or leave them to Pebrik.

  2. 2

    It works in its own branch

    Each task gets its own copy of your code and its own branch, with dependencies installed, inside a sandbox. It asks before going outside its folder.

  3. 3

    You review and keep it

    See every file it changed and how, then keep the work as a commit, discard it, or open it in your editor.

Bigger jobs

A team of agents, each on the job it's best at.

For a bigger change, a planner reads the code and proposes tasks in stages. Change any of it, or ask the planner to, then start.

  • Side by side. Builders work on their tasks at the same time, and can message each other when their work meets.
  • Checked and merged in order. Pebrik Code runs each task's checks and merges the tasks onto the job's branch one by one.
  • The right model for each role. Low-cost models read and check; the strongest plan and review.
  • A report at the end. What the job did, what wasn't tried, how to try it, and what each task cost.
Inside your company's rules

On your computer, through your company's Pebrik.

The code stays on your machine. The model calls go through Pebrik, so the same models, budgets and records apply as everywhere else.

Every vendor's models

Use the models your admins allow, from Anthropic, OpenAI and Google, without a separate subscription for each.

Budgets that hold

Every task and job has a spending limit. Pebrik Code stops at it, and you can pause or stop it at any time.

Sandboxed

Tasks run inside your computer's sandbox and ask before reaching outside their folder.

On the record

Usage and spend are recorded with the rest of your company's Pebrik use.

Secrets stay put

Files git ignores, like .env, are copied into a task only after you say yes.

Your branches, your call

Nothing reaches your branch until you keep it. Work ends up on a task or job branch for you to merge.

Works with your projects

Fits how your developers already work.

Any git repository

Bring your project

Choose a folder with a git repository, and Pebrik Code takes it from there.

Set up for you

Node and Python ready

Dependencies go in from the project's lockfile, and Python projects get their own environment.

Your checkout or its own

Work where you want

A task can use its own copy of the code, or work in your checkout alongside you.

Give your developers a team.

Pebrik Code is a desktop app for Mac, with your company's Pebrik behind it. Tell us about your developers, and we'll set them up.

Ask about Pebrik Code About Pebrik