Fyndry

Slack-native AI engineers for your team.

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.

runs the agent you already use
Claude Code Codex GitHub
One thread, one sandbox, one pull request.
A thread of light entering a sealed cube and leaving as a branch graph

How it works

  1. Ask in SlackMention Fyndry in a project channel, or reply in the thread.
  2. It works in a sandboxAn isolated container with your repo, tools and no raw secrets.
  3. You get a pull requestWith a live test run and screenshots that prove the fix.
  4. CI stays greenIt reads Jenkins, fixes what it broke, and reports back in the thread.

Overview

Every channel carries its own playbook.

A channel's prompt holds the repo's conventions, its test and evidence rules, and the traps that break CI. New work inherits what the team already learned.

Credential-safe by design.

Sandboxes only ever see placeholder tokens. Real GitHub, Jenkins and Slack credentials are injected at the network edge, per channel, for approved hosts only.

Evidence, not claims.

Every pull request ships a live end-to-end run with screenshots, and proof the test fails without the fix. Nothing merges on an agent's word.

Self-hosted, on your terms.

Runs on your own Kubernetes, so repos, logs and secrets stay inside your boundary. Built on the open-source Centaur kernel, with Claude Code, Codex or Amp behind one execution model.

A sealed container, a membrane of light, and services beyond it Stacked screenshot frames beside a checkmark

Humans still merge

Fyndry never merges on its own initiative. It opens the pull request, proves the change, keeps CI green and waits. The call stays with the reviewer.