emerik ⎯ by bloomteq
emerikNativeLink

Build faster.
Keep the
context.

Your agents shouldn’t rebuild what already exists. Or rediscover what your team already knows.

NativeLink reuses the build work. emerik preserves the decisions behind it. Two complementary layers for AI-assisted engineering.

Try emerik with NativeLink today

One setup flow. A shared cache. Context that stays with your code.

One codebase. Two kinds of memory.
The knowledge loop and the build loop emerik connects decisions, changes, and reviews. NativeLink connects builds, cached results, and reuse. Your code is the common ground. This is a conceptual illustration. emerik The knowledge loop NativeLink The build loop Decide Change Review Build Cache Reuse Your code
Knowledge worth keepingWork worth reusing
Same code.More momentum.
Shared across agents, humans, and CIContext that lives with your codeYour infrastructure. Your workflow.

The connection

Less repetition.
On both sides of the build.

A faster build loop gets your team to the next result. A durable knowledge loop helps them understand what to do with it.

emerikby Bloomteq

Remember why
the code is this way.

Keep decisions, constraints, and review history alongside the code. Give the next engineer or agent a starting point that survives the last conversation.

The decision and its reasoning The constraint every change must respect The review that carries the context forward
Meet emerik
NativeLinkRemote build cache

Reuse the work
that’s already done.

Let agents, developers, and CI share cached build results. With remote execution, distribute build actions beyond a single machine.

AgentsDevelopersCI
One shared cache
Explore NativeLink

From setup to everyday work

A build result.
With the story attached.

The connection uses evidence your build tool already writes. emerik brings that evidence into the knowledge loop, without becoming another build service.

Choose a step to explore how the workflow fits together.

emerik ⎯ the knowledge layer

Start with what the team knows.

The setup skill assesses your repository, identifies a suitable cache or execution path, and turns the work into an initiative with clear next steps.

Repository context ⎯ decisions ⎯ implementation plan

Made to fit

Keep your build system.
Connect the understanding.

A familiar build stack

NativeLink works with Bazel, Buck2, Pants, Siso, BuildStream, and CMake through recc. It’s the remote build cache example for this workflow, built on a shared protocol.

Evidence, close to the code

emerik reads local build logs. Credentials stay outside the knowledge store, and the cache-evidence check reads results without launching another build.

A path for your team

The integration supports self-hosted NativeLink and Enterprise. Start with caching; consider remote execution when your toolchains and infrastructure are ready.

Get started

Give your next change
a better starting point.

Choose NativeLink during emerik setup. Your agent assesses the repository and creates an initiative to connect your build cache, with clear goals and checks along the way.

01Get started with emerikKeep your engineering context with your code.02Set up NativeLinkPut a shared remote build cache to work.