[GH-ISSUE #5864] Feature request: AI-agent skills — architecture context, safe composite operations, and impact analysis for agent-driven network management #12186

New Issue

saavagebueno · 2026-08-05T01:32:36-04:00

saavagebueno commented

2026-08-05 01:32:36 -04:00

Originally created by @renne on GitHub (Apr 12, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5864

AI agents (GitHub Copilot, Claude, Cursor, etc.) that manage NetBird networks via the REST API or MCP servers consistently cause unexpected side effects and hard-to-diagnose failures. The root cause is not missing API coverage (that is addressed in #5787) — it is that agents have no model of NetBird's architectural planes, cross-plane dependencies, and mutation semantics.

Concrete failures encountered in production

#	Failure	Root cause
1	`DELETE /api/peers/{id}` returns HTTP 412	Peer is still referenced as a network router. No warning, no helpful error. Agent had no way to know the dependency existed.
2	`PATCH /api/peers/{id}` with `{"ssh_enabled":true}` returns HTTP 500	The endpoint requires a full-object `PUT`, not `PATCH`. The community MCP server's `update_netbird_peer` tool uses `PATCH` internally, so this failure is systematic.
3	Adding peer to group `servers` silently opened unexpected access	Group `servers` was the destination of an `any → servers: allow all` policy. Agent saw only the group membership change; the ACL side effect was invisible without a full policy graph read.
4	Nameserver group created before its peer group existed	DNS config is orphaned. No error returned. Agent sequenced operations bottom-up instead of top-down.
5	Re-provisioned peer hostname created `docker1-proxy-2`, `-3`, … ghosts	Agent did not wipe `/var/lib/netbird/` before re-registering. Ghost peers accumulated in group memberships and policies indefinitely.
6	Reverse-proxy service returned 502 for wildcard domain resource	Using a wildcard `*.docker1` resource as `target_id` silently breaks `host` forwarding. Non-wildcard per-hostname resources are required. Agent had no way to know this constraint.
7	Agent tried to configure relay/signal server via management API	Relay and signal servers are deployment-level services; they have no public management API. Agent wasted many API calls before failing.

These failures share a common theme: the agent treated NetBird as a flat set of CRUD endpoints and lacked knowledge of:

Which architectural plane each resource belongs to
How planes connect through the group concept
Which operations have side effects across plane boundaries
The required ordering of resource creation and deletion

Describe the solution you'd like

1. Architecture reference for AI agents (LLMS.txt + in-repo agent context)

Publish a machine-readable architecture description at https://app.netbird.io/llms.txt (and in the docs / repo under docs/agent-context/) following the llmstxt.org standard. The content must cover all NetBird architectural planes and their interactions:

The planes

Plane	Components	Key agent misconceptions to correct
Data plane	WireGuard tunnels between peers, relay-server (TURN-like, for symmetric NAT), signal-server (WebRTC rendezvous for peer discovery)	"Deleting a peer only removes a config entry." — Reality: it immediately tears down all WireGuard tunnels to/from that peer. Services behind it become unreachable.
Routing plane	Network resources (IP/CIDR/domain addresses), network routers (peer + metric + masquerade flag), routes (subnet/exit-node/domain), posture checks	Agents create resources without assigning a router, or delete a routing peer before removing the resource reference — leaving unreachable resources in the graph.
DNS plane	Nameserver groups (domain → upstream DNS server, distributed to peers via groups), DNS zones + records (authoritative internal zones, v0.63+), DNS settings (disabled management groups per account)	Agents sequence DNS operations bottom-up; create nameserver groups before referenced peer groups; don't know that NetBird auto-creates a `nb.<domain>` sub-zone alongside user-created zones.
ACL/Policy plane	Groups (peer members + resource members — the universal connector), policies (rules: source groups × destination groups × protocol/ports × direction), posture checks (device compliance gates)	Agents modify group membership without understanding that groups simultaneously govern data-plane ACLs, DNS distribution, and routing scope. A single group membership change can open/close access across all three planes at once.
Management plane	Management server (REST API + gRPC push to peers), web dashboard, setup keys (enrollment tokens), personal access tokens, users + roles, events log	Agents use `PATCH` (returns 500 for peers); don't know that management pushes config to online peers asynchronously — a config change only takes effect when the peer next connects.
Relay & Signal	Relay server (TURN-like relay for NAT traversal, no public management API), signal server (WebRTC signaling, no public management API)	Agents attempt to configure relay/signal via management API — these are deployment-level services not exposed in the public API.
Reverse proxy	Network resource with `target_type: domain`, DNS Wildcard Routing setting (off by default), requires `ipset` on Alpine-based containers	Agents use `target_type: "peer"` (400), use wildcard resources as `target_id` (502 silent failure), forget to enable DNS Wildcard Routing toggle in Settings.

How planes connect: the Group concept

Groups are the universal connector across all planes. This is the most critical concept for AI agents to internalize:

Peers ──────────────────┐
Network Resources ──────┤ → Group members
                        │
Group ──────────────────┼──→ Policy sources/destinations (ACL plane)
                        ├──→ Route distribution scope (routing plane)
                        ├──→ Nameserver group distribution targets (DNS plane)
                        └──→ Setup key default groups (management plane)

Consequence: any operation that changes group membership (adding/removing a peer or resource) has potential side effects in every other plane. Agents must read the full group graph before modifying membership.

Lifecycle ordering rules

Agents must follow these ordering constraints to avoid 412/400/orphan errors:

Create order (top-down):

Groups (no dependencies)
Peers / network resources (may reference groups)
Policies, routes, nameserver groups (reference groups)
Network routers (reference peers + networks)
DNS zones + records (reference networks)

Delete order (bottom-up):

DNS zone records → DNS zones
Network routers (unlink before deleting the referenced peer)
Routes, policies, nameserver groups
Peers, network resources
Groups (only after all members removed)

2. Dependency graph / impact-analysis API

Before any destructive or structural mutation, agents need to know what depends on a resource. Proposed endpoint:

GET /api/resources/{type}/{id}/dependents

Or as an impact-analysis operation:

POST /api/agent/impact-analysis
Body: {"operation": "delete", "resource_type": "peer", "resource_id": "abc123"}

Example response:

{
  "resource": {"type": "peer", "id": "abc123", "name": "docker1-proxy"},
  "safe_to_proceed": false,
  "blocking_dependencies": [
    {
      "type": "network_router",
      "id": "r1",
      "network_id": "net1",
      "network_name": "docker1-net",
      "required_action": "PUT /api/networks/net1/routers/r1 with peer_id set to null or reassign to another peer"
    }
  ],
  "soft_dependencies": [
    {
      "type": "group",
      "id": "g1",
      "name": "servers",
      "effect": "Removing peer from group will affect 2 policies and 1 nameserver group"
    }
  ]
}

This single endpoint prevents the #1 cause of 412 errors and enables agents to plan safe multi-step deletions automatically.

3. Topology introspection endpoint

AI agents currently need 10+ sequential API calls to build a mental model of a network. A single topology endpoint would replace this:

GET /api/agent/topology

Returns the full network as a labelled graph suitable for AI reasoning:

{
  "peers": [{"id": "...", "name": "...", "groups": [...], "connected": true}],
  "groups": [{"id": "...", "name": "...", "peer_ids": [...], "resource_ids": [...]}],
  "policy_graph": [
    {
      "policy_id": "p1",
      "name": "servers-access",
      "source_groups": ["g-clients"],
      "destination_groups": ["g-servers"],
      "effect": "allow tcp:443,80 bidirectional"
    }
  ],
  "routing_graph": [
    {
      "network_id": "net1",
      "resources": [{"id": "res1", "address": "192.168.1.0/24"}],
      "routers": [{"peer_id": "peer1", "metric": 100, "masquerade": true, "peer_connected": true}]
    }
  ],
  "dns_graph": [
    {
      "nameserver_group_id": "ns1",
      "domains": ["bartschnet.de"],
      "nameservers": ["10.0.0.7:53"],
      "distribution_groups": ["g-all-peers"]
    }
  ]
}

4. Safe composite operations

High-level operations that handle ordering, dependency checks, and cleanup atomically:

Endpoint	What it does
`DELETE /api/agent/peers/{id}/safe`	Checks all dependencies, unlinks routers, removes from groups, deletes peer — or returns a structured error if manual intervention is required
`POST /api/agent/expose-service`	Creates network + resource + router + nameserver group + policy in one atomic operation with rollback on failure
`POST /api/agent/validate`	Validates a planned set of API mutations without executing them; returns ordering issues, dependency conflicts, and side effects

5. Official agent skill files

Provide maintained agent skill files in the repository (docs/agent-skills/) that encode safe, plane-aware workflows for popular agent frameworks (GitHub Copilot SKILL.md, Anthropic tool definitions):

Skill	Purpose
`netbird-architecture.md`	Explains all planes, components, and cross-plane interactions — the prerequisite for all other skills
`netbird-add-peer.md`	Onboard a peer: enrollment key selection, group assignment, policy check, DNS configuration
`netbird-expose-service.md`	Expose a service end-to-end: network resource + router + policy + DNS (includes reverse-proxy variant and required settings)
`netbird-remove-peer.md`	Safe peer removal: impact analysis → router unlink → group cleanup → delete
`netbird-audit-network.md`	Summarize current topology across all planes; identify orphaned resources, open any-to-any policies, missing routers
`netbird-debug-connectivity.md`	Diagnose why peer A cannot reach resource B: walk the ACL plane → routing plane → DNS plane → data plane

Describe alternatives you've considered

CQ/knowledge-base workaround — Documenting agent gotchas in a local knowledge base (e.g. CQ) per deployment. Works for individual operators but doesn't scale and requires re-discovery per agent session.
Thin MCP wrapper only (#5787) — Exposes raw API as tools but does not prevent agents from calling them in wrong order or without understanding side effects. Necessary but not sufficient.
Agent prompts with inline instructions — Embedding ordering rules in system prompts is fragile, token-expensive, and not version-controlled alongside the API.

Additional context

This request is complementary to #5787 (official MCP server). #5787 provides the tools; this request provides the intelligence and safety guardrails that make those tools usable without side effects.
Related: #5810 (expose peer LAN IPs) — the topology endpoint proposed here would benefit from that data.
The llmstxt.org standard is already adopted by many developer tools (Vercel, Stripe, etc.) as the canonical way to provide AI-agent context.
NetBird's architectural complexity (7 planes, groups as universal connector, ordering constraints) is unusually high for a management API. Without explicit agent guidance, incorrect usage is the expected default — not the exception.

Originally created by @renne on GitHub (Apr 12, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5864 ## Is your feature request related to a problem? Please describe. AI agents (GitHub Copilot, Claude, Cursor, etc.) that manage NetBird networks via the REST API or MCP servers consistently cause **unexpected side effects and hard-to-diagnose failures**. The root cause is not missing API coverage (that is addressed in #5787) — it is that agents have no model of NetBird's **architectural planes, cross-plane dependencies, and mutation semantics**. ### Concrete failures encountered in production | # | Failure | Root cause | |---|---|---| | 1 | `DELETE /api/peers/{id}` returns HTTP 412 | Peer is still referenced as a network router. No warning, no helpful error. Agent had no way to know the dependency existed. | | 2 | `PATCH /api/peers/{id}` with `{"ssh_enabled":true}` returns HTTP 500 | The endpoint requires a full-object `PUT`, not `PATCH`. The community MCP server's `update_netbird_peer` tool uses `PATCH` internally, so this failure is systematic. | | 3 | Adding peer to group `servers` silently opened unexpected access | Group `servers` was the destination of an `any → servers: allow all` policy. Agent saw only the group membership change; the ACL side effect was invisible without a full policy graph read. | | 4 | Nameserver group created before its peer group existed | DNS config is orphaned. No error returned. Agent sequenced operations bottom-up instead of top-down. | | 5 | Re-provisioned peer hostname created `docker1-proxy-2`, `-3`, … ghosts | Agent did not wipe `/var/lib/netbird/` before re-registering. Ghost peers accumulated in group memberships and policies indefinitely. | | 6 | Reverse-proxy service returned 502 for wildcard domain resource | Using a wildcard `*.docker1` resource as `target_id` silently breaks `host` forwarding. Non-wildcard per-hostname resources are required. Agent had no way to know this constraint. | | 7 | Agent tried to configure relay/signal server via management API | Relay and signal servers are deployment-level services; they have no public management API. Agent wasted many API calls before failing. | These failures share a common theme: the agent treated NetBird as a flat set of CRUD endpoints and lacked knowledge of: - Which architectural **plane** each resource belongs to - How planes **connect** through the group concept - Which operations have **side effects** across plane boundaries - The required **ordering** of resource creation and deletion --- ## Describe the solution you'd like ### 1. Architecture reference for AI agents (LLMS.txt + in-repo agent context) Publish a machine-readable architecture description at `https://app.netbird.io/llms.txt` (and in the docs / repo under `docs/agent-context/`) following the [llmstxt.org](https://llmstxt.org) standard. The content must cover all NetBird architectural **planes** and their interactions: #### The planes | Plane | Components | Key agent misconceptions to correct | |---|---|---| | **Data plane** | WireGuard tunnels between peers, relay-server (TURN-like, for symmetric NAT), signal-server (WebRTC rendezvous for peer discovery) | "Deleting a peer only removes a config entry." — Reality: it immediately tears down all WireGuard tunnels to/from that peer. Services behind it become unreachable. | | **Routing plane** | Network resources (IP/CIDR/domain addresses), network routers (peer + metric + masquerade flag), routes (subnet/exit-node/domain), posture checks | Agents create resources without assigning a router, or delete a routing peer before removing the resource reference — leaving unreachable resources in the graph. | | **DNS plane** | Nameserver groups (domain → upstream DNS server, distributed to peers via groups), DNS zones + records (authoritative internal zones, v0.63+), DNS settings (disabled management groups per account) | Agents sequence DNS operations bottom-up; create nameserver groups before referenced peer groups; don't know that NetBird auto-creates a `nb.<domain>` sub-zone alongside user-created zones. | | **ACL/Policy plane** | Groups (peer members + resource members — the universal connector), policies (rules: source groups × destination groups × protocol/ports × direction), posture checks (device compliance gates) | Agents modify group membership without understanding that groups simultaneously govern data-plane ACLs, DNS distribution, and routing scope. A single group membership change can open/close access across all three planes at once. | | **Management plane** | Management server (REST API + gRPC push to peers), web dashboard, setup keys (enrollment tokens), personal access tokens, users + roles, events log | Agents use `PATCH` (returns 500 for peers); don't know that management pushes config to online peers asynchronously — a config change only takes effect when the peer next connects. | | **Relay & Signal** | Relay server (TURN-like relay for NAT traversal, no public management API), signal server (WebRTC signaling, no public management API) | Agents attempt to configure relay/signal via management API — these are deployment-level services not exposed in the public API. | | **Reverse proxy** | Network resource with `target_type: domain`, DNS Wildcard Routing setting (off by default), requires `ipset` on Alpine-based containers | Agents use `target_type: "peer"` (400), use wildcard resources as `target_id` (502 silent failure), forget to enable DNS Wildcard Routing toggle in Settings. | #### How planes connect: the Group concept **Groups are the universal connector across all planes.** This is the most critical concept for AI agents to internalize: ``` Peers ──────────────────┐ Network Resources ──────┤ → Group members │ Group ──────────────────┼──→ Policy sources/destinations (ACL plane) ├──→ Route distribution scope (routing plane) ├──→ Nameserver group distribution targets (DNS plane) └──→ Setup key default groups (management plane) ``` **Consequence:** any operation that changes group membership (adding/removing a peer or resource) has potential side effects in every other plane. Agents must read the full group graph before modifying membership. #### Lifecycle ordering rules Agents must follow these ordering constraints to avoid 412/400/orphan errors: **Create order (top-down):** 1. Groups (no dependencies) 2. Peers / network resources (may reference groups) 3. Policies, routes, nameserver groups (reference groups) 4. Network routers (reference peers + networks) 5. DNS zones + records (reference networks) **Delete order (bottom-up):** 1. DNS zone records → DNS zones 2. Network routers (unlink before deleting the referenced peer) 3. Routes, policies, nameserver groups 4. Peers, network resources 5. Groups (only after all members removed) ### 2. Dependency graph / impact-analysis API Before any destructive or structural mutation, agents need to know what depends on a resource. Proposed endpoint: ``` GET /api/resources/{type}/{id}/dependents ``` Or as an impact-analysis operation: ``` POST /api/agent/impact-analysis Body: {"operation": "delete", "resource_type": "peer", "resource_id": "abc123"} ``` **Example response:** ```json { "resource": {"type": "peer", "id": "abc123", "name": "docker1-proxy"}, "safe_to_proceed": false, "blocking_dependencies": [ { "type": "network_router", "id": "r1", "network_id": "net1", "network_name": "docker1-net", "required_action": "PUT /api/networks/net1/routers/r1 with peer_id set to null or reassign to another peer" } ], "soft_dependencies": [ { "type": "group", "id": "g1", "name": "servers", "effect": "Removing peer from group will affect 2 policies and 1 nameserver group" } ] } ``` This single endpoint prevents the #1 cause of 412 errors and enables agents to plan safe multi-step deletions automatically. ### 3. Topology introspection endpoint AI agents currently need 10+ sequential API calls to build a mental model of a network. A single topology endpoint would replace this: ``` GET /api/agent/topology ``` Returns the full network as a **labelled graph** suitable for AI reasoning: ```json { "peers": [{"id": "...", "name": "...", "groups": [...], "connected": true}], "groups": [{"id": "...", "name": "...", "peer_ids": [...], "resource_ids": [...]}], "policy_graph": [ { "policy_id": "p1", "name": "servers-access", "source_groups": ["g-clients"], "destination_groups": ["g-servers"], "effect": "allow tcp:443,80 bidirectional" } ], "routing_graph": [ { "network_id": "net1", "resources": [{"id": "res1", "address": "192.168.1.0/24"}], "routers": [{"peer_id": "peer1", "metric": 100, "masquerade": true, "peer_connected": true}] } ], "dns_graph": [ { "nameserver_group_id": "ns1", "domains": ["bartschnet.de"], "nameservers": ["10.0.0.7:53"], "distribution_groups": ["g-all-peers"] } ] } ``` ### 4. Safe composite operations High-level operations that handle ordering, dependency checks, and cleanup atomically: | Endpoint | What it does | |---|---| | `DELETE /api/agent/peers/{id}/safe` | Checks all dependencies, unlinks routers, removes from groups, deletes peer — or returns a structured error if manual intervention is required | | `POST /api/agent/expose-service` | Creates network + resource + router + nameserver group + policy in one atomic operation with rollback on failure | | `POST /api/agent/validate` | Validates a planned set of API mutations without executing them; returns ordering issues, dependency conflicts, and side effects | ### 5. Official agent skill files Provide **maintained agent skill files** in the repository (`docs/agent-skills/`) that encode safe, plane-aware workflows for popular agent frameworks (GitHub Copilot `SKILL.md`, Anthropic tool definitions): | Skill | Purpose | |---|---| | `netbird-architecture.md` | Explains all planes, components, and cross-plane interactions — the prerequisite for all other skills | | `netbird-add-peer.md` | Onboard a peer: enrollment key selection, group assignment, policy check, DNS configuration | | `netbird-expose-service.md` | Expose a service end-to-end: network resource + router + policy + DNS (includes reverse-proxy variant and required settings) | | `netbird-remove-peer.md` | Safe peer removal: impact analysis → router unlink → group cleanup → delete | | `netbird-audit-network.md` | Summarize current topology across all planes; identify orphaned resources, open any-to-any policies, missing routers | | `netbird-debug-connectivity.md` | Diagnose why peer A cannot reach resource B: walk the ACL plane → routing plane → DNS plane → data plane | --- ## Describe alternatives you've considered 1. **CQ/knowledge-base workaround** — Documenting agent gotchas in a local knowledge base (e.g. CQ) per deployment. Works for individual operators but doesn't scale and requires re-discovery per agent session. 2. **Thin MCP wrapper only (#5787)** — Exposes raw API as tools but does not prevent agents from calling them in wrong order or without understanding side effects. Necessary but not sufficient. 3. **Agent prompts with inline instructions** — Embedding ordering rules in system prompts is fragile, token-expensive, and not version-controlled alongside the API. --- ## Additional context - This request is **complementary** to #5787 (official MCP server). #5787 provides the *tools*; this request provides the *intelligence and safety guardrails* that make those tools usable without side effects. - Related: #5810 (expose peer LAN IPs) — the topology endpoint proposed here would benefit from that data. - The [llmstxt.org](https://llmstxt.org) standard is already adopted by many developer tools (Vercel, Stripe, etc.) as the canonical way to provide AI-agent context. - NetBird's architectural complexity (7 planes, groups as universal connector, ordering constraints) is unusually high for a management API. Without explicit agent guidance, incorrect usage is the expected default — not the exception.

Sign in to join this conversation.

Branches Tags

main

claude/agent-network-test-cases-p743vw

android/gui-integration

revert/component-types

feat-post_quantum_ml_kem

ice-stun-wg-demux

dependabot/npm_and_yarn/proxy/web/npm_and_yarn-b39864987c

agent-network-setup-poc

dependabot/go_modules/aws-sdk-8f849ebaed

dependabot/github_actions/actions-a940c7c866

dependabot/go_modules/otel-e34c790afd

dependabot/go_modules/testcontainers-de325c0dd6

dependabot/go_modules/wireguard-dbd6b95108

dependabot/go_modules/pion-5f703e1eca

dependabot/go_modules/gorm-2271c8195b

fix-login-needed-check

dependabot/go_modules/google.golang.org/grpc-1.82.1

fix/ui-gtk3-support

enterprise-traefik-and-migration-fixes

disambiguate_p2p_metrics

revert/component-types-hookup

embedded-vnc

feature/ios-ssh

docs/agent-network-docs-update

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.106.3

dependabot/go_modules/github.com/pion/stun/v3-3.1.5

fix-ssh-authorized-users-multi-rule

peer-acl-multi-source

reverse-proxy-crowdsec-appsec

reverse-proxy-allow-match-or

client-local-metrics

lazy-conn-per-peer

lazy-conn-rosenpass

dependabot/go_modules/github.com/gopacket/gopacket-1.7.0

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.6

dependabot/go_modules/github.com/pires/go-proxyproto-0.15.0

dependabot/go_modules/github.com/jackc/pgx/v5-5.10.0

dependabot/go_modules/github.com/oapi-codegen/runtime-1.6.0

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.4

dependabot/go_modules/github.com/pkg/sftp-1.13.11

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.20.0

ssh-windows-privilege-check

fix/explicit-cors-handling

fix/remove-math-rand

test/gui-memory-leak-fix

fix/ui-status-dispatch

install-script-ui-dependencies

fix/grpc-get-network-map

fix/subscribe-status-coalesce

fix/tray-menu-item-leak

fix/windows-tray-race

feature/changeset

worktree-dns-route-qtype-fallthrough

mdm_integration

mlsmaycon-patch-2

feat/agent-network-ollama

proxy-tunnel-cache-ttl-env

coderabbitai/utg/1e5b0a5

grpc-acl

test/battery-drain

components-impl-drop-indexes-use-xids-no-resource-policy-map

fix/nmap-relevant-groups

e2e-guardrail-blocks-unselected-model

fix/lazyconn-cold-start-allowed-ips

vertex-guardrails-model-access-e2e

add-atomic-cache-ops

refactor/relay-foreign-cache

ci/trigger-release-tests

feature/kimi-3-agent-networks-dns-warmup

feature/dns-lazy-conn-warmup

daemon-ipc-acl

feature/ui-translation-key-parity-check

refactor/relay-foreign-cache-tests

fix/lazyconn-idle-keep-wg-peer

dmitri-propagate-auth-grant-types-on-combined

0.74.7-branch

diagnose-empty-vs-corrupt-state

windows-sleep-detector

fix/cli-up-wait-for-daemon

rp_key_persistency

feature/native-grpc

0.74.6-branch

0.74.6-branch-sync

0.74.5-branch-sync

0.74.4-branch

fix/remove-stale-peers-removal

fix/remove-stale-proxy-logic

fix/nsis-preserve-autostart-on-upgrade

refactor/peer-event-bus

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.3

dependabot/go_modules/github.com/pkg/sftp-1.13.10

components-impl-drop-indexes

fix-reset-aggregation-window-flake

dependabot/go_modules/github.com/pion/dtls/v3-3.1.5

0.74.x

fix/relay-states-lock

update-process-pkg

update-gopsutil-v4

fix/relay_states_lock

increase-sysinfo-timeout

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

dependabot/go_modules/github.com/eko/gocache/store/redis/v4-4.2.6

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.3

fix/fail-to-create-upnp-port-mapping-on-opnsense-firewall

0.74.3-branch

fix/routeselector-atomic-exit-node

netmap_progressive_alignment

nmap/components-impl

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

dependabot/go_modules/github.com/oapi-codegen/runtime-1.4.2

dependabot/go_modules/github.com/gopacket/gopacket-1.6.1

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.19.0

dependabot/go_modules/github.com/pires/go-proxyproto-0.12.0

fix/signal-watchdog-sync-stop

docs/agent-network

test/affected-logic

fix/revert-ice-filter

refactor/simplify-affected-peers

pascal-filter-policies-by-direction

claude/lock-contention-peer-connect-g8t6au

dmitri-filter-policies-by-direction

refactor/migrate-profiles-to-go

profile-bindings-ios

fix/skip-restart-unchanged-route

fix/mgmt-cache-async-resolve

refactor/wails-update-105

client_lifetime_serialization_refactor

fix/browser-ssh-2

fix/ipv6-and-netstack-accept-loop

fix/browser-ssh

profile-id-name-test

refactor/mgmt-bootstrap

feat/getting-started-unified-wizard

socket-grpc-permissions

fix/mysql-index-migration

windows-dns-firewall

tests/enable-race-on-tests

ui-refactor-gtk3

feature/affected-peers-grpc

profile-id

lazyconn-first-packet-fix-v2

claude/focused-gates-VMTgb

ui-tray-linux-leftclick

fix/ctx-enrichment

daemon-owner

feature/android-client-ssh

worktree-accept-ra-forwarding

nmap/combined-deploy

task/align_protobuff_toolset

feature/session-extend

add-json-yaml-flags

refactor/ephemeral-cleanup

claude/webtransport-relay-wasm-mUjY9

claude/vnc-udp-feasibility-6KB1U

fix/wgport-config

e2e-windows-dns-combined

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

release/0.68.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: DYNR/netbird#12186