Layer III · Engineering

Instruction in plain language. Source in your repository.

You describe the strategy, the tool or the report you want. It is written into your project as code you can read, change, version and keep, in the same tree your editor and git history are looking at. The engineering a desk would staff, held in one workspace on your machine.

Talk to Blackshore Agency

What it holds

Strategies, tools and internal applications, written as source into your own repository.

01An AI engineer, on your choice of engine

One engine contract, several engines behind it, switched per conversation. Claude Code and OpenAI Codex are the engines we have driven end to end, and only engines we have verified are offered.

02Output is files, not a transcript

Every change lands on disk in your repository, where it can be reviewed and reverted. Nothing you build depends on a hosted runtime you must stay subscribed to.

03A real editor and real terminals

Python, TypeScript, Rust, C++ and the rest, with split panes and search across the tree. The terminals are your shell, your PATH and your installed runtimes; the app never intercepts a command.

04Version control from the first line

Status, diffs, history, branches, commits, push and pull, in the place you write. Research you cannot reproduce is not research, so the work is versioned from the start.

AI engineer · Editor & terminal · Git · Stack Apps

Due diligence

Questions asked first.

Who owns the code it writes?

You do. It is written to your disk, in your repository, and the IP is yours, whether the AI or a Blackshore Agency engineer wrote it.

Does my code leave my machine?

The editor, terminals, git and every process run locally, and nothing is uploaded to run them. The one connection out is the AI engine you choose.

Which platforms does it run on?

macOS on Apple Silicon and Intel, Windows x64, and Linux as an AppImage or .deb. Installers are code-signed and the app updates itself.

Your infrastructure. Your keys. Our engineers on call.