CorenessOpen source · MIT

An agent that answers to the project.

A small family of projects about governed agent work: what a project accepts, remembers and allows to be spent — written down, so the agent can be held to it.

What a profile gets

A page of its own

The profile's overview: which bundles the profile carries, and what a session or a plugin has to be told.

The MCP servers

One card per server: its address, its transport, its tools and a switch whose effect lands in the profile.

A limiter that waits

A request over the limit takes its turn in a queue — nothing is limited as the package ships.

Custom providers

Services the platform does not ship a client for, brought in through the profile and kept with the rest of it.

The journal

The environment's memory: what changed and what a participant did, kept as records a session can read.

The rules in force

A project's conventions carried in every request, through the platform's own prompt registry.

Two ways in

In a terminal

dsh plugin --profile desktop add github:Vensus137/Coreness-DSH

In the application

Plugins Add plugin

github:Vensus137/Coreness-DSH

Two projects, one position

Coreness Kit

The rules of the work, written down and taken whole. A snapshot a project carries.

Vensus137/Coreness-Kit

Coreness for DeepSeek Harness

The same idea, carried into an environment: a face, a memory and a brake for a profile.

Vensus137/Coreness-DSH