The AI engineer that lives in Slack.

Describe the work in a channel. Fyndry picks it up in an isolated sandbox, opens a pull request with live test evidence, and watches CI until it is green.

Request access Open Console

runs the agent you already use

Claude Code Codex GitHub

Lives in Slack. Mention Fyndry in a project channel and the thread becomes the session.
One sandbox per thread. An isolated container with your repo and tools, torn down after.
No raw secrets inside it. Sandboxes hold placeholders; real tokens are swapped in at the network edge.
Your harness. Claude Code, Codex and Amp behind one execution model.
Your model. Pick the model and the reasoning effort per chat.
Pull requests with proof. A live end-to-end run, screenshots, and the test failing without the fix.
It watches CI. Reads Jenkins, fixes what it broke, and reports back in the thread.
Skills and schedules. Give it repeatable procedures, and put the recurring ones on a cron.
It checks its own deploys. Read-only cloud connections confirm what is serving before it says a fix is live.

bumi

Ali8:41 AM

@fyndry the dealer form accepts a phone number with letters, fix it and add a regression test

FyndryAPP8:43 AM

On it. Validation lives in the shared package, so I will fix it there and cover the form and the API.

Ran 24 commands, e2e spec green, screenshots attached

PR #612 fix(dealer): reject letters in phone numbers

Jenkins / bumi passed

One thread, one sandbox, one pull request.

The console, for the work that outgrew a thread.

Every chat in one place, with the skills the agents can use, the tasks you have put on a schedule, and read-only connections to the clouds they check their own deploys against.

Open the console →

Questions

Which agents can it run?: Claude Code, Codex and Amp, behind one execution model. You pick the model and the reasoning effort when you start a chat, and the thread keeps what it started on.
Where does it run?: On your own Kubernetes, so repos, logs and secrets stay inside your boundary. It is built on the open-source Centaur kernel.
What can it reach?: Only what you grant. Each channel is a principal with its own roles, and what it may reach — which repos, which hosts, which cloud projects — is granted in the console and enforced at the proxy. The sandbox itself never holds a real credential.
Does it merge by itself?: No. It opens the pull request, proves the change, keeps CI green and waits. The call stays with the reviewer.
Do we have to work in Slack?: No. The console has the same chats, and you can start one there. Slack is where most teams already are, so that is where it listens.
How does it know our conventions?: Each channel carries its own prompt: the repo’s conventions, its test and evidence rules, and the traps that break CI. New work inherits what the team already wrote down.

Add Fyndry to your team.

The engineer who shows their work.

Request access Open Console