Nexus
Управление и наблюдаемость ИИ-агентов
Видьте всё, что делают ваши ИИ-агенты, блокируйте недопустимое и сокращайте расходы. Nexus фиксирует каждое действие, применяет политики в реальном времени и отслеживает каждого агента, идентичность и соединение.
Every agent action, captured at the source
Nexus wraps the agent runtime itself. Events stream from the terminal to a durable local ledger, then roll up to the governance console: who did what, in which repo, on which terminal.
| Event | When | What Nexus records |
|---|---|---|
| session | Agent session starts | Terminal ID, user (git email), repo, branch, commit, model and provider |
| prompt | Every prompt submitted | Fingerprint and length only at the default privacy tier. No prompt text leaves the machine |
| tool_action | Before every tool call | Tool, target, and a blocked flag with the policy reason when Nexus says no |
| dependency_install | npm / pnpm / yarn / pip / mvn / cargo | Package and version, giving supply-chain visibility for every agent-initiated install |
| file_change | Every edit or write | Repo-relative path plus a protected flag when a policy-guarded file is touched |
| token_usage | Every turn | Input, output, baseline vs. compressed tokens, savings, and cost |
Privacy by default: at the standard capture tier, prompt content is never stored: only a fingerprint and length.
Governance that pays for itself
The same event stream that powers the audit trail meters every token. Nexus attributes AI spend per terminal, per repo, and per user, and measures exactly what context compression and output filtering save you.
Baseline vs. actual
Every turn records baseline tokens, compressed tokens, and the delta, so savings are measured, not estimated. You see the real cost of every session and what it would have cost without optimization.
Cost attribution
Spend rolls up by user, repo, terminal, and model. Runaway sessions and expensive workflows surface immediately instead of at invoice time.
Waste elimination
Per-command output filtering and context compression cut the tokens agents burn on verbose tool output: typically the largest single source of avoidable agent spend.
Trace every agent. Every connection. Every change.
Observability tells you what happened. Nexus also decides what is allowed to happen , and maps the identities and connections behind it all.
In-flight policy blocking
Nexus sits between the agent and your system. Protected files, forbidden commands, and unapproved dependency installs are denied before they execute, with the reason logged to the audit ledger.
Audit trail: prompt → change → why
Every change an agent makes is traceable back through the tool action and the prompt that caused it. Security review stops being archaeology; the trail is already assembled.
Shadow-AI detection
Unmanaged agents, unsanctioned model providers, and unknown non-human identities surface as findings. This is the AI usage your existing SaaS security tooling cannot see.
Identity graph + blast radius
Every agent and non-human identity in one inventory, with a connection graph that answers the question that matters in an incident: if this credential is compromised, what can it reach?
Supply-chain visibility
Agent-initiated package installs are first-class events. Know which agent added which dependency, in which repo, on which terminal, before it ships.
Policy-as-code
Governance rules are declared, versioned, and evaluated continuously, rather than captured as screenshots of settings pages. Findings show exactly which policy failed and where.
Go deeper
Ungated guides on the problems Nexus was built for: no email wall, no PDF download.
Claude Code security
Securing and governing Claude Code in the enterprise.
MCP security best practices
Hardening Model Context Protocol servers and connections.
Agent observability
Why observing agents differs from observing LLM calls.
LLM observability
Tokens, cost, latency, quality, and traces for LLM apps.
Shadow AI
What it is, why it is exploding, and how to detect it.
AI agent governance
Inventory, policy, audit, and enforcement for agents.
Non-human identity
Agents, service accounts, and keys as first-class identities.
Zero trust for AI agents
Never trust the agent by default; verify every action.
Error encyclopedia
Infrastructure and AI-stack errors explained and fixed.
Frequently asked questions
What is Swfte Nexus?
Nexus is an AI-agent governance and observability platform. It captures what coding agents like Claude Code actually do: every session, tool action, file change, dependency install, and token spent. It enforces policy in-flight by blocking violations before they execute, and gives security teams an inventory of agents and non-human identities with an identity graph and blast-radius analysis.
How does Nexus capture agent activity?
A lightweight wrapper hooks the agent runtime (for Claude Code, via native hooks) and streams structured events to a local collector and durable ledger. Events flow to the Nexus console for per-terminal, per-repo, per-user visibility. At the default privacy tier, prompts are captured as fingerprint and length only. No prompt text is stored.
Can Nexus block an agent action, not just log it?
Yes. Nexus evaluates policy before the tool call executes. Protected files, denied commands, and unapproved installs are blocked in-flight, with the reason recorded in the audit trail. That is enforcement, not just observability.
How does Nexus reduce AI spend?
Nexus meters token usage per turn (input, output, baseline versus compressed) and attributes cost per terminal, repo, and user. Teams use it to find runaway sessions, enforce budgets, and measure what context compression and output filtering actually save.
Does Nexus work with agents other than Claude Code?
The capture wrapper is agent-agnostic by design; Claude Code is the deepest integration today via its hook system. The governance console inventories any agent or non-human identity reachable through its connectors, and transcript import covers agents without native hooks.
Is Nexus open source?
Nexus is open-core. Capture, forwarding, and enforcement are open source and always available. The intelligence layer, covering audit trails, metrics, knowledge harvesting, and security modeling, runs against an Enterprise backend: either Nexus cloud or self-hosted.