Engineering guides
Backend systems, Node.js, TypeScript, AI coding, fintech infrastructure, and engineering career proof.
Latest posts
Page 4 of 18Model Context Protocol explained with a practical Node.js example
A practical guide to tool interoperability, with a concrete failure case, implementation trade-offs, and checks engineers can run before shipping.
How to redact API keys before sending code to an AI model
A practical guide to secret flow, with a concrete failure case, implementation trade-offs, and checks engineers can run before shipping.
Prompt injection in README files: how developers should protect AI agents
A practical guide to repository trust, with a concrete failure case, implementation trade-offs, and checks engineers can run before shipping.
How to build a permission system for AI agents
A practical guide to approval scope, with a concrete failure case, implementation trade-offs, and checks engineers can run before shipping.
Local AI agents vs cloud AI agents: privacy, speed, and real trade-offs
A practical guide to the privacy boundary, with a concrete failure case, implementation trade-offs, and checks engineers can run before shipping.
Nerva architecture explained: how a local-first AI agent should control its own actions
A practical guide to the control spine, with a concrete failure case, implementation trade-offs, and checks engineers can run before shipping.
What Nerva should build first: a realistic roadmap for a local AI agent
A realistic first-release roadmap for Nerva covering local tasks, permissions, context control, model adapters, verification, and the features that can wait.
Nerva privacy settings that would actually help developers
A practical privacy settings model for Nerva with local-only mode, cloud approval, path rules, redaction, retention, and visible task history.
Using Nerva to debug a Node.js backend without losing the thread
A focused Node.js debugging workflow for Nerva: capture the error, select relevant context, propose a fix, run a narrow test, and record what was verified.
Using Nerva to understand an unfamiliar JavaScript repository
A practical workflow for using Nerva to map an unfamiliar JavaScript or TypeScript repository while keeping context, edits, and tool access controlled.
How Nerva should recover when an AI tool call fails
A safe failure-recovery design for Nerva that explains errors, avoids silent escalation, preserves state, and asks before changing scope.
How Nerva can verify an AI action instead of trusting its final answer
A verification-first workflow for Nerva: check diffs, exit codes, tests, file state, and expected outcomes after an AI agent uses a tool.
Browser actions in Nerva: permission rules for an AI that can click
How Nerva could safely handle browser automation by showing destinations, actions, form data, downloads, and external side effects before approval.
Terminal command approval in Nerva: a safer way to run developer tools
A practical command-approval policy for Nerva: show the exact command, working directory, environment, network use, and verification before execution.
Why Nerva should show a diff before editing your code
A diff-first workflow for Nerva that lets developers review proposed edits, protect uncommitted work, approve precise writes, and verify tests afterward.
Prompt injection in repositories: how Nerva should treat untrusted instructions
How Nerva can handle prompt injection in READMEs, issue comments, web pages, and downloaded files without letting untrusted text rewrite agent permissions.
Nerva secret redaction: how to keep API keys out of AI context
A practical secret-redaction workflow for Nerva: detect credentials, minimize context, preview removals, and block unsafe cloud requests.
How Nerva can connect multiple AI providers without locking you in
A provider adapter design for Nerva that keeps local models, compatible APIs, quotas, costs, errors, and user-selected routing separate.
Choosing a local model for Nerva on a normal laptop
A practical guide to choosing a local model for Nerva based on memory, context size, speed, task difficulty, privacy, and verification.
How Nerva could use SQLite for local task history and memory
A practical local storage design for Nerva using SQLite for tasks, approvals, context records, model routes, and verification history.
Why Nerva needs a Rust permission engine for sensitive actions
A practical explanation of Nerva's planned Rust permission engine and why file access, commands, secrets, network calls, and browser actions need an independent boundary.
Nerva's tool gateway: why an AI agent should not call tools directly
How Nerva's planned tool gateway can turn model proposals into narrow, validated operations for files, terminal commands, browsers, and other tools.
How Nerva should choose a model for each developer task
A practical model-selection policy for Nerva: match local or cloud models to privacy, capability, context size, speed, cost, and reliability.
Nerva context manager explained: selecting the right files for an AI task
How Nerva's planned context manager can select focused files, imports, tests, and logs without sending an entire repository to a model.
How Nerva's task manager could keep long AI work understandable
A practical task-management design for Nerva: checkpoints, resumable steps, approvals, failures, and clear progress for multi-step AI work.
Nerva architecture explained: the control spine behind a local-first AI agent
A practical explanation of Nerva's planned architecture: task manager, context manager, model router, agent loop, tool gateway, permissions, and verification.
What unlimited means in Nerva's local-first AI model
An honest guide to Nerva's planned unlimited experience: no artificial app message cap, but real provider quotas, device limits, model costs, and permission boundaries still apply.
Nerva vs a normal AI chatbot: what changes when the agent can use your computer
A simple comparison of Nerva and ordinary AI chatbots, including local context, tools, permissions, model choice, privacy, and the risks of letting an agent act.
Nerva's context firewall: keeping private files out of the wrong AI request
How Nerva can classify, minimize, and review context before it reaches a local model, cloud provider, tool, or agent task.
How Nerva should handle permissions before an AI agent takes action
A practical design for Nerva's planned permission engine: separate model suggestions from file edits, terminal commands, network access, and other actions that need user control.