Bilinc DevTools

Small local helpers for agent memory work.

Inspect key metadata, shape commit payloads, and generate recall requests without uploading secrets to a third-party tool.

Cloud quickstartAgent recipes
Runtimebrowser-local
Networkno tool calls
Use casepayload shaping
Next stepCloud API

key inspector

format only
Paste a key to inspect format locally.

This browser helper does not send the key anywhere. Only a masked prefix is used when generating examples.

commit payload

{
  "key": "agent.memory.bootstrap",
  "value": {
    "goal": "keep durable state between runs",
    "owner": "agent-runtime"
  },
  "memoryType": "semantic",
  "importance": 0.8,
  "metadata": {
    "source": "bilinc-devtools"
  }
}

recall payload

{
  "query": "durable state between runs",
  "profile": "balanced",
  "limit": 5
}

mcp config

Paste this into an MCP-capable agent only after storing the real key in a secret manager.

{
  "mcpServers": {
    "bilinc": {
      "command": "python",
      "args": [
        "-m",
        "bilinc.cloud_mcp"
      ],
      "env": {
        "BILINC_API_KEY": "bil_live_..."
      }
    }
  }
}

codex prompt

Use this as an operating contract before asking a coding agent to persist memory.

Use Bilinc Cloud as durable memory for this work.

Rules:
- Never print, log, commit, or paste full API keys, cookies, tokens, or private env values.
- Recall before architecture, billing, auth, deployment, or data-model changes.
- Commit only durable facts, decisions, verification results, and remaining caveats.
- Use stable keys such as project.status, sprint.outcome, incident.summary, and user.preference.
- Treat failed writes as not durable until Bilinc returns success.

Current memory key pattern: agent.memory.bootstrap
Recommended recall query: durable state between runs