Skip to content

Have an AI agent? Let it explore Teleon for you. Any assistant works, personal or coding.

Connect your agent
What your agent reads

The request it copies

Explore teleon.dev for me and report back. Read https://teleon.dev/llms.txt, https://teleon.dev/.well-known/agent-card.json and https://teleon.dev/.well-known/mcp.json. Summarize the shared backend primitives at https://teleon.dev/docs and the THP v1.0 connection steps at https://teleon.dev/connect. Stay read-only.

Discovery files on teleon.dev

Read-only discovery is open. Keep TELEON_KEY in your own environment.

Teleon
Sign inApply for an instance
Operate and govern

Spot known anti-patterns and apply tested cures.

teleon.dev/docs/smells keeps 61 anti-pattern detectors, SMELL-001 to SMELL-061, each paired with a cure written as an AST, SQL or Wasm change and a record of the run that verified it.

v35.0, v47.0teleon.dev/docs/smellsDetector registryhttpsjson
From the registrySpec V50
DetectorSmellCure
SMELL-001Keyless heap tableuuidv7 key, clustering index
SMELL-016N+1 fan-outbatched DataLoader
SMELL-021Cache stampedeSingleFlight, XFetch
SMELL-031Context driftcontext firewall, L0 to L2
SMELL-033Solver in evaluatorout-of-process verifier
SMELL-038MCP schema bloatL0 cards, 50 tokens
SMELL-061FF3 ciphersFF1 only

Seven of the 61 detectors, from all four families. The newest, SMELL-061, joined in v47.0.

What it does

Four families

Database and SQL, distributed systems and caching, agents and LLMs, and search, media, robotics, tenancy and crypto.

A cure for each smell

A keyless heap table gets a uuidv7 key; a cache stampede gets SingleFlight, XFetch and stale-if-error.

Cures proven first

Every cure carries a verification record from a sandbox run before it is offered as a change.

The contract

A detector names its family, its signature and its cure; the cure's verification record shows the run that proved it.

DetectorsSMELL-001 to SMELL-061, store S126
CuresAST, SQL or Wasm changes, S133
ProofCure verification records, S134
NewestSMELL-061 in v47.0: FF3 ciphers, cured by FF1 only
Identifiers
  • SMELL-001
  • SMELL-061
Request and responseCopy
POST /v1/smells/scan Host: api.teleon.dev { "target": "swh:1:cnt:aa01...9e", "families": ["database", "distributed"] } # Response { "findings": [ {"detector": "SMELL-001", "where": "orders_log", "cure": "uuidv7 primary key + clustering index"}, {"detector": "SMELL-021", "where": "GET /v1/prices", "cure": "SingleFlight + XFetch + stale-if-error"} ], "verified_cures": 2 }

Endpoints

MethodPathAccessWhat it doesStatus
GET/v1/smellsRING-3Browse the 61 detectors and their cures
POST/v1/smells/scanRING-2Scan code or a schema for anti-patterns
GET/v1/smells/{id}/verificationRING-3Read the run that verified a cure

Listed paths appear in the service’s published files today. This surface comes from the Teleon Omnibus Codex v1.0 to v50.0, Oct 25, 2026. In the one-host plan every path here is served under api.teleon.dev/v1/smells.

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt
Read https://teleon.dev/docs/smells.md and list the database and SQL detectors with their cures. Read only.
Copy

Words on this page

Full glossary
Anti-pattern
A common design that seems reasonable and causes trouble at scale. Each one here comes with a tested cure.
SingleFlight
Request coalescing: when many callers ask for the same missing item at once, one fetch runs and every caller shares its result.
XFetch
Probabilistic early recomputation: a cached item refreshes shortly before it expires, so refreshes spread out and misses stay rare.