Self-hosted · Open source · Apache-2.0
Observal
A registry for your coding agent extensions, with an insight engine built in. Set it up, define the scope, and share your Skills, MCPs and Agents with your team.
01:47 am
Three teams wrote the same code review skill this quarter. None of them knew.
Claude Code · Codex · Cursor · Kiro · Goose
Her company runs all of them. Every team keeps its own copies.
Maya, platform team
She decided that was the last time.
Every skill, MCP and agent her team uses now lives in one place.
01 · Registry
Every skill, MCP server, hook and prompt your teams build, versioned and reviewed in one place. Pick a harness and pull the whole agent with one command.
02 · ARD Discover
Describe the task, not the package name. Observal speaks Agentic Resource Discovery, so any ARD client can ask your registry what exists.
03 · Sharing
Teamspaces give every team its own namespace. Keep one private or make it public after review, and everything in it installs as team/agent.
04 · Traces
Every session from every harness becomes a structured trace. Prompts, tool calls, MCP round trips, tokens and errors, captured by hooks.
05 · Insights
Insights live on each agent. The report names what is going wrong, the numbers that prove it, and the prompt changes that fix it.
One agent · every harness
Write it once. It lands the right way in every tool your team runs.
Agentic coding
The agentic coding paradigm shift.
You no longer write every line. You direct agents in loops, steer them, and ship. Watch one work on this very section.
claude-code · ~/observal-site
hooks → observal 0 events
- Direct, don't typeSet the goal in plain language. The agent scopes the work and writes it.
- Steer the loopIt proposes, you correct. One sentence redirects it mid-flight, with no code to undo.
- Ship on your termsThe output reflects your intent, not the agent's assumptions. Every trace proves it.
Own your stack
Self-hosted. Open source. Yours.
One command brings up the registry, analytics and databases with Docker Compose. Postgres, ClickHouse and Redis run on your infrastructure, so components, sessions and data never leave it. Apache-2.0, no lock-in.
maya@studio · ~