ruuf agents

New agent

Settings

Import spec… Export spec

Fills in as you talk to Gru, or by hand. A spec is this form as a file: download a template, fill it in, and import it here or run agents create <file>.

Identity

Choose a picture… PNG, JPEG, WebP or GIF, up to 1 MB. Shown square, small.

Slug Lowercase, hyphens. Cannot change later. Name

Purpose Identity prompt The head of the cached prompt. Who it is, how it answers, what it never does.

Prompt version Bump it when the identity changes. Runs

Model

Credential prefix Chat uses the selected provider's credential. Consolidation uses the xAI key; embeddings use the Azure pair. Embeddings deployment

Chat provider Chat model Chat effort Consolidation model

Daily token budget

Slack

Slack app prefix Names AGENT_SLACK_<PREFIX>_SIGNING_SECRET / _BOT_TOKEN. Empty: no Slack. Answers

Channel ids Allowed bot member IDs Only these bots can trigger the agent, and only with an explicit @mention. Empty blocks all bots.

The Slack app itself is one manifest this service renders for the agent; the steps below are the whole of it, in order. Save the agent first; the manifest carries its slug.

Who can use it

Visibility On the page, in Slack and over MCP alike. Private is the default for anything created here. People Slack handles or @ruuf.solar emails, comma separated. You are always in. They can see it and talk to it; only you change it.

What it owns

Repositories One per line. Owned paths Globs, one per line. A coding session asks who owns a file before editing it.

Excluded paths

Core memories

Identity that lives in the definition: rules it never breaks, facts it always knows. Seeded into the memory when you save.

In a coding session Description The sentence the subagent picker reads. Empty: no subagent. Which plugin tools a coding session may call is set per plugin, on the Plugins page. Never

Available

Install a plugin and the agent has its tools on the next turn. Settings are checked when you save; the check button runs the plugin's health check.

Correos capturados por Pinky. Publicado en Slack significa que el equipo recibió una propuesta pendiente de revisión y envío manual.

Every time this agent thought, or a coding session used one of its tools. A run is a turn with its tokens; a step is one tool call under it, with what went in and what came back.

budget 6000 tokens

This is the text an agent is given: the same bytes for a Slack turn and for @perestroika in a coding session. The stable block is cached and only moves when a memory does.

stable

volatile

Both arms rank separately and are fused by reciprocal rank, so a row both found can sit above a closer one. The number is the vector similarity, not the order. Nothing below 0.35 comes back at all. Every hit bumps a recall count, which is what decides who gets into the cached prefix.

Whatever lands here is short‑term, whoever writes it. Identifiers are masked before the row exists. Try a RUT, an email or a phone number and watch what is stored.

since

A thread that has been away is told what moved while it was gone. This goes in the volatile block only, so the cached prefix survives. Nothing new produces nothing at all.

What the nightly consolidation does, on demand: every short‑term note nobody has dreamed about yet is shown to the agent beside the long‑term rows nearest to it, and it answers with one operation per note: add, update, drop or contradiction. This spends the agent's xAI key. A dry run asks the model and writes nothing.

The lookup a coding session makes before it edits a file.