Skip to main content Crate nomoreide_core Copy item path Source agent_context The debugging context packet an agent reads before it touches a service. agent_env What the coding agents on this machine are configured with. agent_info Everything the two agents have on this machine. agent_profiles Saved bundles of MCP servers, skills, and plugins. agent_runtime Driving a real agent CLI (Claude Code or Codex) through one headless turn. agent_sessions Agent change-sets: what an agent session touched, pinned to the snapshot
taken before its first tool call. agent_settings Each coding agent’s settings file — the one a person edits by hand —
which is not the MCP config crate::agent_env agent_transcripts app_settings Machine-wide settings: ~/.config/nomoreide/settings.json. approval_broker Bridges an agent CLI’s tool-permission hook to whoever is watching the run. bundle Bundle start/stop ordering (mirrors startBundle/stopBundle in
src/core/process-manager.ts). claude_settings One setting inside ~/.claude/settings.json, and nothing else in it. cloudflare_actions Write-capable Cloudflare Pages operations, deliberately separate from the
read-safe cloudflare_manager — the same split as git_manager / git write
commands, and the Rust counterpart of src/core/cloudflare-actions.ts. cloudflare_auth The token the Cloudflare integration should use — the Rust counterpart of
src/core/cloudflare-auth.ts. cloudflare_context Resolves “which Cloudflare account does this token mean” — the Rust
counterpart of src/core/cloudflare-context.ts. cloudflare_manager Read-safe Cloudflare Pages REST client — the Rust counterpart of
src/core/cloudflare-manager.ts. cloudflare_provider Cloudflare Pages seen through the vendor-neutral deploy contract. compose Docker Compose services. config config_files Finding, browsing, and resolving a service’s configuration files. context_library context_snapshot The context library’s listing , which is more than its notes. db Read-only access to the databases a user has registered. directories Listing a directory for the in-app pickers. docker Read-mostly Docker introspection: whatever is on this machine, registered as
a nomoreide service or not. env_file Reading .env files the way the reference does. error_inbox Deduped error and stack-trace incidents detected across managed service logs. event_sink exec_file execFile, including how it reports a failure.external_terminal filesystem fix_loop Turn an error-inbox incident into one agent task whose result is reviewable. git_identity Commit identity derived from the GitHub account selected for a repository. git_manager Read-safe Git. github_auth github_context Which GitHub repository a directory is, and which account speaks for it. github_manager The GitHub REST client. github_oauth GitHub’s OAuth device flow: the two calls that turn a code the user types
into a token this machine can store. home Where the user’s dotfiles live. host_metrics What the machine itself is doing: CPU, memory, load, uptime and disk. http_inspector A reverse proxy that watches one service’s HTTP traffic. jetbrains_import Import a JetBrains project’s run configurations and data sources. js_json JSON.parse failures, worded the way V8 words them.js_number Number(text) and JSON.stringify(number), which are two different things.locale String.prototype.localeCompare, as far as this program needs it.log_sources Saved log sources: a file, a remote file, or a command that someone reads on
demand. log_store log_volume How much a service said, and how badly, over the range its graph covers. mcp_auth Live auth state for every MCP server an agent has, asked of the agent’s own
CLI. metrics_store Rolling CPU and memory, for the host and for each running service. one_time_skills port_utils process_manager project_overview Per-project summaries for the all-projects lens. providers The provider layer: how NoMoreIDE reaches a deploy platform, and in what
shape it reports back. read_only_files The read-only remote file protocol, shared by SSH and docker exec. repo_create Create a brand-new Git project from nothing: make the directory, git init
it, and seed a README so the folder is not empty. repo_match Which registered repository a working directory belongs to. repo_onboard Cloning a repository from a URL, and the URL parsing that names it. repro_bundle The “share my bug” document for one error-inbox incident. runtime_registry service_definition Reading a service definition out of loosely-typed arguments, and refusing
one that describes nothing runnable. service_graph Service dependency ordering (mirrors src/core/service-graph.ts). service_health One service’s health verdict, computed from what the runtime already knows. service_test Running a candidate command briefly, to answer “does this actually start?” snapshot_manager Working-tree checkpoints, kept out of the branch namespace. ssh_servers Saved and discovered SSH servers, connection checks, and read-only metrics. ssh_setup What the machine already has for connecting somewhere, and the two terminals
that fill the gaps. system_processes The host’s process table, and the one guarded way to end a process on it. terminal Daemon-owned PTY sessions: the terminal tabs the dashboard renders, the
agent sessions it launches, and moving one of those into macOS Terminal.app
and back. test_runner Run a service’s test command and report it as it happens. timeline The debug timeline: a short, ordered account of what the runtime did. tool_call_store A bounded, in-memory feed of MCP tool calls. usage_history Token and cost totals, kept over time. usage_info What the two agents say they have spent. vercel_actions Write-capable Vercel operations, deliberately separate from the read-safe
vercel_manager — the same split as git_manager / git write commands, and
the Rust counterpart of src/core/vercel-actions.ts. vercel_auth Where a Vercel token comes from — the Rust counterpart of
src/core/vercel-auth.ts. vercel_context Resolves “which Vercel account and project does this repository mean” —
the Rust counterpart of src/core/vercel-context.ts. vercel_manager Read-safe Vercel REST client — the Rust counterpart of
src/core/vercel-manager.ts. vercel_oauth Browser sign-in for Vercel: OAuth 2.0 authorization code + PKCE against a
loopback redirect (RFC 8252, “OAuth 2.0 for Native Apps”). vercel_provider Vercel seen through the vendor-neutral deploy contract. vultr_actions Write-capable Vultr power operations, deliberately separate from the
read-safe vultr_manager — the same split as git_manager / git write
commands, db::peek / nomoreide_actions::db, and cloudflare_manager /
cloudflare_actions. The Rust half of src/core/vultr-actions.ts. vultr_auth Which Vultr credential to use, and what to say when there is none. vultr_context Turning stored configuration into a usable Vultr client, and reporting what
the dashboard’s status panel shows. vultr_manager The one place a Vultr API call is made. vultr_provider Vultr as host provider #1. workflow_triggers Binding an event to a workflow. workflows User-owned git/GitHub workflows: the shipped templates, and the shape a
saved one has to have. zod_report The validator’s report, worded and shaped the way zod words and shapes it.