Navigate back to the previous page in browser history. Requires browser_navigate to be called first.

Send a raw Chrome DevTools Protocol (CDP) command. Escape hatch for browser operations not covered by browser_navigate, browser_click, browser_console, etc.

**Requires a reachable CDP endpoint.** Available when the user has run '/browser connect' to attach to a running Chrome, or when 'browser.cdp_url' is set in config.yaml. Not currently wired up for cloud backends (Browserbase, Browser Use, Firecrawl) — those expose CDP per session but live-session routing is a follow-up. Camofox is REST-only and will never support CDP. If the tool is in your toolset at all, a CDP endpoint is already reachable.

**CDP method reference:** https://chromedevtools.github.io/devtools-protocol/ — use web_extract on a method's URL (e.g. '/tot/Page/#method-handleJavaScriptDialog') to look up parameters and return shape.

**Common patterns:**
- List tabs: method='Target.getTargets', params={}
- Handle a native JS dialog: method='Page.handleJavaScriptDialog', params={'accept': true, 'promptText': ''}, target_id=<tabId>
- Get all cookies: method='Network.getAllCookies', params={}
- Eval in a specific tab: method='Runtime.evaluate', params={'expression': '...', 'returnByValue': true}, target_id=<tabId>
- Set viewport for a tab: method='Emulation.setDeviceMetricsOverride', params={'width': 1280, 'height': 720, 'deviceScaleFactor': 1, 'mobile': false}, target_id=<tabId>

**Usage rules:**
- Browser-level methods (Target.*, Browser.*, Storage.*): omit target_id and frame_id.
- Page-level methods (Page.*, Runtime.*, DOM.*, Emulation.*, Network.* scoped to a tab): pass target_id from Target.getTargets.
- **Cross-origin iframe scope** (Runtime.evaluate inside an OOPIF, Page.* targeting a frame target, etc.): pass frame_id from the browser_snapshot frame_tree output. This routes through the CDP supervisor's live connection — the only reliable way on Browserbase where stateless CDP calls hit signed-URL expiry.
- Each stateless call (without frame_id) is independent — sessions and event subscriptions do not persist between calls. For stateful workflows, prefer the dedicated browser tools or use frame_id routing.

CDP method name, e.g. 'Target.getTargets', 'Runtime.evaluate', 'Page.handleJavaScriptDialog'.

Method-specific parameters as a JSON object. Omit or pass {} for methods that take no parameters.

Optional. Target/tab ID from Target.getTargets result (each entry's 'targetId'). Use for page-level methods at the top-level tab scope. Mutually exclusive with frame_id.

Optional. Out-of-process iframe (OOPIF) frame_id from browser_snapshot.frame_tree.children[] where is_oopif=true. When set, routes the call through the CDP supervisor's live session for that iframe. Essential for Runtime.evaluate inside cross-origin iframes, especially on Browserbase where fresh per-call CDP connections can't keep up with signed URL rotation. For same-origin iframes, use parent contentWindow/contentDocument from Runtime.evaluate at the top-level page instead.

Timeout in seconds (default 30, max 300).

Click on an element identified by its ref ID from the snapshot (e.g., '@e5'). The ref IDs are shown in square brackets in the snapshot output. Requires browser_navigate and browser_snapshot to be called first.

The element reference from the snapshot (e.g., '@e5', '@e12')

Get browser console output and JavaScript errors from the current page. Returns console.log/warn/error/info messages and uncaught JS exceptions. Use this to detect silent JavaScript errors, failed API calls, and application warnings. Requires browser_navigate to be called first. When 'expression' is provided, evaluates JavaScript in the page context and returns the result — use this for DOM inspection, reading page state, or extracting data programmatically.

If true, clear the message buffers after reading

JavaScript expression to evaluate in the page context. Runs in the browser like DevTools console — full access to DOM, window, document. Return values are serialized to JSON. Example: 'document.title' or 'document.querySelectorAll("a").length'

Respond to a native JavaScript dialog (alert / confirm / prompt / beforeunload) that is currently blocking the page.

**Workflow:** call ``browser_snapshot`` first — if a dialog is open, it appears in the ``pending_dialogs`` field with ``id``, ``type``, and ``message``. Then call this tool with ``action='accept'`` or ``action='dismiss'``.

**Prompt dialogs:** pass ``prompt_text`` to supply the response string. Ignored for alert/confirm/beforeunload.

**Multiple dialogs:** if more than one dialog is queued (rare — happens when a second dialog fires while the first is still open), pass ``dialog_id`` from the snapshot to disambiguate.

**Availability:** only present when a CDP-capable backend is attached — Browserbase sessions, local Chrome via ``/browser connect``, or ``browser.cdp_url`` in config.yaml. Not available on Camofox (REST-only) or the default Playwright local browser (CDP port is hidden).

'accept' clicks OK / returns the prompt text. 'dismiss' clicks Cancel / returns null from prompt(). For ``beforeunload`` dialogs: 'accept' allows the navigation, 'dismiss' keeps the page.

Response string for a ``prompt()`` dialog. Ignored for other dialog types. Defaults to empty string.

Specific dialog to respond to, from ``browser_snapshot.pending_dialogs[].id``. Required only when multiple dialogs are queued.

Get a list of all images on the current page with their URLs and alt text. Useful for finding images to analyze with the vision tool. Requires browser_navigate to be called first.

Navigate to a URL in the browser. Initializes the session and loads the page. Must be called before other browser tools. For simple information retrieval, prefer web_search or web_extract (faster, cheaper). For plain-text endpoints — URLs ending in .md, .txt, .json, .yaml, .yml, .csv, .xml, raw.githubusercontent.com, or any documented API endpoint — prefer curl via the terminal tool or web_extract; the browser stack is overkill and much slower for these. Use browser tools when you need to interact with a page (click, fill forms, dynamic content). Returns a compact page snapshot with interactive elements and ref IDs — no need to call browser_snapshot separately after navigating.

The URL to navigate to (e.g., 'https://example.com')

Press a keyboard key. Useful for submitting forms (Enter), navigating (Tab), or keyboard shortcuts. Requires browser_navigate to be called first.

Key to press (e.g., 'Enter', 'Tab', 'Escape', 'ArrowDown')

Scroll the page in a direction. Use this to reveal more content that may be below or above the current viewport. Requires browser_navigate to be called first.

Direction to scroll

Get a text-based snapshot of the current page's accessibility tree. Returns interactive elements with ref IDs (like @e1, @e2) for browser_click and browser_type. full=false (default): compact view with interactive elements. full=true: complete page content. Snapshots over 8000 chars are truncated or LLM-summarized. Requires browser_navigate first. Note: browser_navigate already returns a compact snapshot — use this to refresh after interactions that change the page, or with full=true for complete content.

If true, returns complete page content. If false (default), returns compact view with interactive elements only.

Type text into an input field identified by its ref ID. Clears the field first, then types the new text. Requires browser_navigate and browser_snapshot to be called first.

The element reference from the snapshot (e.g., '@e3')

The text to type into the field

Take a screenshot of the current page and analyze it with vision AI. Use this when you need to visually understand what's on the page - especially useful for CAPTCHAs, visual verification challenges, complex layouts, or when the text snapshot doesn't capture important visual information. Returns both the AI analysis and a screenshot_path that you can share with the user by including MEDIA:<screenshot_path> in your response. Requires browser_navigate to be called first.

What you want to know about the page visually. Be specific about what you're looking for.

If true, overlay numbered [N] labels on interactive elements. Each [N] maps to ref @eN for subsequent browser commands. Useful for QA and spatial reasoning about page layout.

clarify

Ask the user a question when you need clarification, feedback, or a decision before proceeding. Supports two modes:

1. **Multiple choice** — provide up to 4 choices. The user picks one or types their own answer via a 5th 'Other' option.
2. **Open-ended** — omit choices entirely. The user types a free-form response.

Use this tool when:
- The task is ambiguous and you need the user to choose an approach
- You want post-task feedback ('How did that work out?')
- You want to offer to save a skill or update memory
- A decision has meaningful trade-offs the user should weigh in on

Do NOT use this tool for simple yes/no confirmation of dangerous commands (the terminal tool handles that). Prefer making a reasonable default choice yourself when the decision is low-stakes.

The question to present to the user.

Choices:
Up to 4 answer choices. Omit this parameter entirely to ask an open-ended question. When provided, the UI automatically appends an 'Other (type your answer)' option.

cronjob

Manage scheduled cron jobs with a single compressed tool.

Use action='create' to schedule a new job from a prompt or one or more skills.
Use action='list' to inspect jobs.
Use action='update', 'pause', 'resume', 'remove', or 'run' to manage an existing job.

To stop a job the user no longer wants: first action='list' to find the job_id, then action='remove' with that job_id. Never guess job IDs — always list first.

Jobs run in a fresh session with no current-chat context, so prompts must be self-contained.
If skills are provided on create, the future cron run loads those skills in order, then follows the prompt as the task instruction.
On update, passing skills=[] clears attached skills.

NOTE: The agent's final response is auto-delivered to the target. Put the primary
user-facing content in the final response. Cron jobs run autonomously with no user
present — they cannot ask questions or request clarification.

Important safety rule: cron-run sessions should not recursively schedule more cron jobs.

One of: create, list, update, pause, resume, remove, run

Required for update/pause/resume/remove/run

For create: the full self-contained prompt. If skills are also provided, this becomes the task instruction paired with those skills.

For create/update: '30m', 'every 2h', '0 9 * * *', or ISO timestamp

Optional human-friendly name

Optional repeat count. Omit for defaults (once for one-shot, forever for recurring).

Omit this parameter to auto-deliver back to the current chat and topic (recommended). Auto-detection preserves thread/topic context. Only set explicitly when the user asks to deliver somewhere OTHER than the current conversation. Values: 'origin' (same as omitting), 'local' (no delivery, save only), or platform:chat_id:thread_id for a specific destination. Examples: 'telegram:-1001234567890:17585', 'discord:#engineering', 'sms:+15551234567'. WARNING: 'platform:chat_id' without :thread_id loses topic targeting.

Optional ordered list of skill names to load before executing the cron prompt. On update, pass an empty array to clear attached skills.

Optional per-job model override. If provider is omitted, the current main provider is pinned at creation time so the job stays stable.

Provider name (e.g. 'openrouter', 'anthropic'). Omit to use and pin the current provider.

Model name (e.g. 'anthropic/claude-sonnet-4', 'claude-sonnet-4')

Optional path to a Python script that runs before each cron job execution. Its stdout is injected into the prompt as context. Use for data collection and change detection. Relative paths resolve under ~/.hermes/scripts/. On update, pass empty string to clear.

Optional job ID or list of job IDs whose most recent completed output is injected into the prompt as context before each run. Use this to chain cron jobs: job A collects data, job B processes it. Each entry must be a valid job ID (from cronjob action='list'). Note: injects the most recent completed output — does not wait for upstream jobs running in the same tick. On update, pass an empty array to clear.

Optional list of toolset names to restrict the job's agent to (e.g. ["web", "terminal", "file", "delegation"]). When set, only tools from these toolsets are loaded, significantly reducing input token overhead. When omitted, all default tools are loaded. Infer from the job's prompt — e.g. use "web" if it calls web_search, "terminal" if it runs scripts, "file" if it reads files, "delegation" if it calls delegate_task. On update, pass an empty array to clear.

Optional absolute path to run the job from. When set, AGENTS.md / CLAUDE.md / .cursorrules from that directory are injected into the system prompt, and the terminal/file/code_exec tools use it as their working directory — useful for running a job inside a specific project repo. Must be an absolute path that exists. When unset (default), preserves the original behaviour: no project context files, tools use the scheduler's cwd. On update, pass an empty string to clear. Jobs with workdir run sequentially (not parallel) to keep per-job directories isolated.

Spawn one or more subagents to work on tasks in isolated contexts. Each subagent gets its own conversation, terminal session, and toolset. Only the final summary is returned -- intermediate tool results never enter your context window.

TWO MODES (one of 'goal' or 'tasks' is required):
1. Single task: provide 'goal' (+ optional context, toolsets)
2. Batch (parallel): provide 'tasks' array with up to delegation.max_concurrent_children items (default 3, configurable via config.yaml, no hard ceiling). All run concurrently and results are returned together. Nested delegation requires role='orchestrator' and delegation.max_spawn_depth >= 2.

WHEN TO USE delegate_task:
- Reasoning-heavy subtasks (debugging, code review, research synthesis)
- Tasks that would flood your context with intermediate data
- Parallel independent workstreams (research A and B simultaneously)

WHEN NOT TO USE (use these instead):
- Mechanical multi-step work with no reasoning needed -> use execute_code
- Single tool call -> just call the tool directly
- Tasks needing user interaction -> subagents cannot use clarify
- Durable long-running work that must outlive the current turn -> use cronjob (action='create') or terminal(background=True, notify_on_complete=True) instead. delegate_task runs SYNCHRONOUSLY inside the parent turn: if the parent is interrupted (user sends a new message, /stop, /new) the child is cancelled with status='interrupted' and its work is discarded. Children cannot continue in the background.

IMPORTANT:
- Subagents have NO memory of your conversation. Pass all relevant info (file paths, error messages, constraints) via the 'context' field.
- If the user is writing in a non-English language, or asked for output in a specific language / tone / style, say so in 'context' (e.g. "respond in Chinese", "return output in Japanese"). Otherwise subagents default to English and their summaries will contaminate your final reply with the wrong language.
- Subagent summaries are SELF-REPORTS, not verified facts. A subagent that claims "uploaded successfully" or "file written" may be wrong. For operations with external side-effects (HTTP POST/PUT, remote writes, file creation at shared paths, publishing), require the subagent to return a verifiable handle (URL, ID, absolute path, HTTP status) and verify it yourself — fetch the URL, stat the file, read back the content — before telling the user the operation succeeded.
- Leaf subagents (role='leaf', the default) CANNOT call: delegate_task, clarify, memory, send_message, execute_code.
- Orchestrator subagents (role='orchestrator') retain delegate_task so they can spawn their own workers, but still cannot use clarify, memory, send_message, or execute_code. Orchestrators are bounded by delegation.max_spawn_depth (default 2) and can be disabled globally via delegation.orchestrator_enabled=false.
- Each subagent gets its own terminal session (separate working directory and state).
- Results are always returned as an array, one entry per task.

What the subagent should accomplish. Be specific and self-contained -- the subagent knows nothing about your conversation history.

Background information the subagent needs: file paths, error messages, project structure, constraints. The more specific you are, the better the subagent performs.

Toolsets to enable for this subagent. Default: inherits your enabled toolsets. Available toolsets: 'browser', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'vision', 'web', 'yuanbao'. Common patterns: ['terminal', 'file'] for code work, ['web'] for research, ['browser'] for web interaction, ['terminal', 'file', 'web'] for full-stack tasks.

Task goal

Task-specific context

Toolsets for this specific task. Available: 'browser', 'cronjob', 'discord', 'discord_admin', 'feishu_doc', 'feishu_drive', 'file', 'homeassistant', 'image_gen', 'kanban', 'search', 'session_search', 'skills', 'spotify', 'terminal', 'todo', 'tts', 'vision', 'web', 'yuanbao'. Use 'web' for network access, 'terminal' for shell, 'browser' for web interaction.

Per-task ACP command override (e.g. 'claude'). Overrides the top-level acp_command for this task only.

Per-task ACP args override.

Per-task role override. See top-level 'role' for semantics.

Batch mode: tasks to run in parallel (limit configurable via delegation.max_concurrent_children, default 3). Each gets its own subagent with isolated context and terminal session. When provided, top-level goal/context/toolsets are ignored.

Role of the child agent. 'leaf' (default) = focused worker, cannot delegate further. 'orchestrator' = can use delegate_task to spawn its own workers. Requires delegation.max_spawn_depth >= 2 in config; ignored (treated as 'leaf') when the child would exceed max_spawn_depth or when delegation.orchestrator_enabled=false.

Override ACP command for child agents (e.g. 'claude', 'copilot'). When set, children use ACP subprocess transport instead of inheriting the parent's transport. Enables spawning Claude Code (claude --acp --stdio) or other ACP-capable agents from any parent, including Discord/Telegram/CLI.

Arguments for the ACP command (default: ['--acp', '--stdio']). Only used when acp_command is set. Example: ['--acp', '--stdio', '--model', 'claude-opus-4-6']

Run a Python script that can call Hermes tools programmatically. Use this when you need 3+ tool calls with processing logic between them, need to filter/reduce large tool outputs before they enter your context, need conditional branching (if X then Y else Z), or need to loop (fetch N pages, process N files, retry on failure).

Use normal tool calls instead when: single tool call with no processing, you need to see the full result and apply complex reasoning, or the task requires interactive user input.

Available via `from hermes_tools import ...`:

  web_search(query: str, limit: int = 5) -> dict
    Returns {"data": {"web": [{"url", "title", "description"}, ...]}}
  web_extract(urls: list[str]) -> dict
    Returns {"results": [{"url", "title", "content", "error"}, ...]} where content is markdown
  read_file(path: str, offset: int = 1, limit: int = 500) -> dict
    Lines are 1-indexed. Returns {"content": "...", "total_lines": N}
  write_file(path: str, content: str) -> dict
    Always overwrites the entire file.
  search_files(pattern: str, target="content", path=".", file_glob=None, limit=50) -> dict
    target: "content" (search inside files) or "files" (find files by name). Returns {"matches": [...]}
  patch(path: str, old_string: str, new_string: str, replace_all: bool = False) -> dict
    Replaces old_string with new_string in the file.
  terminal(command: str, timeout=None, workdir=None) -> dict
    Foreground only (no background/pty). Returns {"output": "...", "exit_code": N}

Limits: 5-minute timeout, 50KB stdout cap, max 50 tool calls per script. terminal() is foreground-only (no background or pty).

Scripts run in the session's working directory with the active venv's python, so project deps (pandas, etc.) and relative paths work like in terminal().

Print your final result to stdout. Use Python stdlib (json, re, math, csv, datetime, collections, etc.) for processing between tool calls.

Also available (no import needed — built into hermes_tools):
  json_parse(text: str) — json.loads with strict=False; use for terminal() output with control chars
  shell_quote(s: str) — shlex.quote(); use when interpolating dynamic strings into shell commands
  retry(fn, max_attempts=3, delay=2) — retry with exponential backoff for transient failures

Python code to execute. Import tools with `from hermes_tools import web_search, terminal, ...` and print your final result to stdout.

Generate high-quality images from text prompts. The underlying backend (FAL, OpenAI, etc.) and model are user-configured and not selectable by the agent. Returns either a URL or an absolute file path in the `image` field; display it with markdown ![description](url-or-path) and the gateway will deliver it.

The text prompt describing the desired image. Be detailed and descriptive.

The aspect ratio of the generated image. 'landscape' is 16:9 wide, 'portrait' is 16:9 tall, 'square' is 1:1.

Get a prompt by name from MCP server 'context7'

Name of the prompt to retrieve

Optional arguments to pass to the prompt

List available prompts from MCP server 'context7'

List available resources from MCP server 'context7'

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.

You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Do not call this tool more than 3 times per question.

Exact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user query in the format '/org/project' or '/org/project/version'.

The question or task you need help with. Be specific and include relevant details. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad: 'auth' or 'hooks'. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.

Read a resource by URI from MCP server 'context7'

URI of the resource to read

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Each result includes:
- Library ID: Context7-compatible identifier (format: /org/project)
- Name: Library or package name
- Description: Short summary
- Code Snippets: Number of available code examples
- Source Reputation: Authority indicator (High, Medium, Low, or Unknown)
- Benchmark Score: Quality indicator (100 is the highest score)
- Versions: List of versions if available. Use one of those versions if the user provides a version in their query. The format of the version is /org/project/version.

For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case.

Selection Process:
1. Analyze the query to understand what library/package the user is looking for
2. Return the most relevant match based on:
- Name similarity to the query (exact matches prioritized)
- Description relevance to the query's intent
- Documentation coverage (prioritize libraries with higher Code Snippet counts)
- Source reputation (consider libraries with High or Medium reputation more authoritative)
- Benchmark Score: Quality indicator (100 is the highest score)

Response Format:
- Return the selected library ID in a clearly marked section
- Provide a brief explanation for why this library was chosen
- If multiple good matches exist, acknowledge this but proceed with the most relevant one
- If no good matches exist, clearly state this and suggest query refinements

For ambiguous queries, request clarification before proceeding with a best-guess match.

IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

The question or task you need help with. This is used to rank library results by relevance to what the user is trying to accomplish. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.

Library name to search for and retrieve a Context7-compatible library ID. Use the official library name with proper punctuation — e.g., 'Next.js' instead of 'nextjs', 'Customer.io' instead of 'customerio', 'Three.js' instead of 'threejs'.

memory

Save durable information to persistent memory that survives across sessions. Memory is injected into future turns, so keep it compact and focused on facts that will still matter later.

WHEN TO SAVE (do this proactively, don't wait to be asked):
- User corrects you or says 'remember this' / 'don't do that again'
- User shares a preference, habit, or personal detail (name, role, timezone, coding style)
- You discover something about the environment (OS, installed tools, project structure)
- You learn a convention, API quirk, or workflow specific to this user's setup
- You identify a stable fact that will be useful again in future sessions

PRIORITY: User preferences and corrections > environment facts > procedural knowledge. The most valuable memory prevents the user from having to repeat themselves.

Do NOT save task progress, session outcomes, completed-work logs, or temporary TODO state to memory; use session_search to recall those from past transcripts.
If you've discovered a new way to do something, solved a problem that could be necessary later, save it as a skill with the skill tool.

TWO TARGETS:
- 'user': who the user is -- name, role, preferences, communication style, pet peeves
- 'memory': your notes -- environment facts, project conventions, tool quirks, lessons learned

ACTIONS: add (new entry), replace (update existing -- old_text identifies it), remove (delete -- old_text identifies it).

SKIP: trivial/obvious info, things easily re-discovered, raw data dumps, and temporary task state.

The action to perform.

Which memory store: 'memory' for personal notes, 'user' for user profile.

The entry content. Required for 'add' and 'replace'.

Short unique substring identifying the entry to replace or remove.

Route a hard problem through multiple frontier LLMs collaboratively. Makes 5 API calls (4 reference models + 1 aggregator) with maximum reasoning effort — use sparingly for genuinely difficult problems. Best for: complex math, advanced algorithms, multi-step analytical reasoning, problems benefiting from diverse perspectives.

The complex query or problem to solve using multiple AI models. Should be a challenging problem that benefits from diverse perspectives and collaborative reasoning.

patch

Targeted find-and-replace edits in files. Use this instead of sed/awk in terminal. Uses fuzzy matching (9 strategies) so minor whitespace/indentation differences won't break it. Returns a unified diff. Auto-runs syntax checks after editing.

Replace mode (default): find a unique string and replace it.
Patch mode: apply V4A multi-file patches for bulk changes.

Edit mode: 'replace' for targeted find-and-replace, 'patch' for V4A multi-file patches

File path to edit (required for 'replace' mode)

Text to find in the file (required for 'replace' mode). Must be unique in the file unless replace_all=true. Include enough surrounding context to ensure uniqueness.

Replacement text (required for 'replace' mode). Can be empty string to delete the matched text.

Replace all occurrences instead of requiring a unique match (default: false)

V4A format patch content (required for 'patch' mode). Format:
*** Begin Patch
*** Update File: path/to/file
@@ context hint @@
 context line
-removed line
+added line
*** End Patch

process

Manage background processes started with terminal(background=true). Actions: 'list' (show all), 'poll' (check status + new output), 'log' (full output with pagination), 'wait' (block until done or timeout), 'kill' (terminate), 'write' (send raw stdin data without newline), 'submit' (send data + Enter, for answering prompts), 'close' (close stdin/send EOF).

list poll log wait kill write submit close

Action to perform on background processes

Process session ID (from terminal background output). Required for all actions except 'list'.

Text to send to process stdin (for 'write' and 'submit' actions)

Max seconds to block for 'wait' action. Returns partial output on timeout.

Line offset for 'log' action (default: last 200 lines)

Max lines to return for 'log' action

Read a text file with line numbers and pagination. Use this instead of cat/head/tail in terminal. Output format: 'LINE_NUM|CONTENT'. Suggests similar filenames if not found. Use offset and limit for large files. Reads exceeding ~100K characters are rejected; use offset and limit to read specific sections of large files. NOTE: Cannot read images or binary files — use vision_analyze for images.

Path to the file to read (absolute, relative, or ~/path)

Line number to start reading from (1-indexed, default: 1)

Maximum number of lines to read (default: 500, max: 2000)

Search file contents or find files by name. Use this instead of grep/rg/find/ls in terminal. Ripgrep-backed, faster than shell equivalents.

Content search (target='content'): Regex search inside files. Output modes: full matches with line numbers, file paths only, or match counts.

File search (target='files'): Find files by glob pattern (e.g., '*.py', '*config*'). Also use this instead of ls — results sorted by modification time.

Regex pattern for content search, or glob pattern (e.g., '*.py') for file search

'content' searches inside file contents, 'files' searches for files by name

Directory or file to search in (default: current working directory)

Filter files by pattern in grep mode (e.g., '*.py' to only search Python files)

Maximum number of results to return (default: 50)

Skip first N results for pagination (default: 0)

Output format for grep mode: 'content' shows matching lines with line numbers, 'files_only' lists file paths, 'count' shows match counts per file

Number of context lines before and after each match (grep mode only)

Search your long-term memory of past conversations, or browse recent sessions. This is your recall -- every past session is searchable, and this tool summarizes what happened.

TWO MODES:
1. Recent sessions (no query): Call with no arguments to see what was worked on recently. Returns titles, previews, and timestamps. Zero LLM cost, instant. Start here when the user asks what were we working on or what did we do recently.
2. Keyword search (with query): Search for specific topics across all past sessions. Returns LLM-generated summaries of matching sessions.

USE THIS PROACTIVELY when:
- The user says 'we did this before', 'remember when', 'last time', 'as I mentioned'
- The user asks about a topic you worked on before but don't have in current context
- The user references a project, person, or concept that seems familiar but isn't in memory
- You want to check if you've solved a similar problem before
- The user asks 'what did we do about X?' or 'how did we fix Y?'

Don't hesitate to search when it is actually cross-session -- it's fast and cheap. Better to search and confirm than to guess or ask the user to repeat themselves.

Search syntax: keywords joined with OR for broad recall (elevenlabs OR baseten OR funding), phrases for exact match ("docker networking"), boolean (python NOT java), prefix (deploy*). IMPORTANT: Use OR between keywords for best results — FTS5 defaults to AND which misses sessions that only mention some terms. If a broad OR query returns nothing, try individual keyword searches in parallel. Returns summaries of the top matching sessions.

Search query — keywords, phrases, or boolean expressions to find in past sessions. Omit this parameter entirely to browse recent sessions instead (returns titles, previews, timestamps with no LLM cost).

Optional: only search messages from specific roles (comma-separated). E.g. 'user,assistant' to skip tool outputs.

Max sessions to summarize (default: 3, max: 5).

Manage skills (create, update, delete). Skills are your procedural memory — reusable approaches for recurring task types. New skills go to ~/.hermes/skills/; existing skills can be modified wherever they live.

Actions: create (full SKILL.md + optional category), patch (old_string/new_string — preferred for fixes), edit (full SKILL.md rewrite — major overhauls only), delete, write_file, remove_file.

On delete, pass `absorbed_into=<umbrella>` when you're merging this skill's content into another one, or `absorbed_into=""` when you're pruning it with no forwarding target. This lets the curator tell consolidation from pruning without guessing, so downstream consumers (cron jobs that reference the old skill name, etc.) get updated correctly. The target you name in `absorbed_into` must already exist — create/patch the umbrella first, then delete.

Create when: complex task succeeded (5+ calls), errors overcome, user-corrected approach worked, non-trivial workflow discovered, or user asks you to remember a procedure.
Update when: instructions stale/wrong, OS-specific failures, missing steps or pitfalls found during use. If you used a skill and hit issues not covered by it, patch it immediately.

After difficult/iterative tasks, offer to save as a skill. Skip for simple one-offs. Confirm with user before creating/deleting.

Good skills: trigger conditions, numbered steps with exact commands, pitfalls section, verification steps. Use skill_view() to see format examples.

Pinned skills are off-limits — all write actions refuse with a message pointing the user to `hermes curator unpin <name>`. Don't try to route around this by renaming or recreating.

create patch edit delete write_file remove_file

The action to perform.

Skill name (lowercase, hyphens/underscores, max 64 chars). Must match an existing skill for patch/edit/delete/write_file/remove_file.

Full SKILL.md content (YAML frontmatter + markdown body). Required for 'create' and 'edit'. For 'edit', read the skill first with skill_view() and provide the complete updated text.

Text to find in the file (required for 'patch'). Must be unique unless replace_all=true. Include enough surrounding context to ensure uniqueness.

Replacement text (required for 'patch'). Can be empty string to delete the matched text.

For 'patch': replace all occurrences instead of requiring a unique match (default: false).

Optional category/domain for organizing the skill (e.g., 'devops', 'data-science', 'mlops'). Creates a subdirectory grouping. Only used with 'create'.

Path to a supporting file within the skill directory. For 'write_file'/'remove_file': required, must be under references/, templates/, scripts/, or assets/. For 'patch': optional, defaults to SKILL.md if omitted.

Content for the file. Required for 'write_file'.

For 'delete' only — declares intent so the curator can tell consolidation from pruning without guessing. Pass the umbrella skill name when this skill's content was merged into another (the target must already exist). Pass an empty string when the skill is truly stale and being pruned with no forwarding target. Omitting the arg on delete is supported for backward compatibility but downstream tooling (e.g. cron-job skill reference rewriting) will have to guess at intent.

Skills allow for loading information about specific tasks and workflows, as well as scripts and templates. Load a skill's full content or access its linked files (references, templates, scripts). First call returns SKILL.md content plus a 'linked_files' dict showing available references/templates/scripts. To access those, call again with file_path parameter.

The skill name (use skills_list to see available skills). For plugin-provided skills, use the qualified form 'plugin:skill' (e.g. 'superpowers:writing-plans').

OPTIONAL: Path to a linked file within the skill (e.g., 'references/api.md', 'templates/config.yaml', 'scripts/validate.py'). Omit to get the main SKILL.md content.

List available skills (name + description). Use skill_view(name) to load full content.

Optional category filter to narrow results

terminal

Execute shell commands on a Linux environment. Filesystem usually persists between calls.

Do NOT use cat/head/tail to read files — use read_file instead.
Do NOT use grep/rg/find to search — use search_files instead.
Do NOT use ls to list directories — use search_files(target='files') instead.
Do NOT use sed/awk to edit files — use patch instead.
Do NOT use echo/cat heredoc to create files — use write_file instead.
Reserve terminal for: builds, installs, git, processes, scripts, network, package managers, and anything that needs a shell.

Foreground (default): Commands return INSTANTLY when done, even if the timeout is high. Set timeout=300 for long builds/scripts — you'll still get the result in seconds if it's fast. Prefer foreground for short commands.
Background: Set background=true to get a session_id. Two patterns:
  (1) Long-lived processes that never exit (servers, watchers).
  (2) Long-running tasks with notify_on_complete=true — you can keep working on other things and the system auto-notifies you when the task finishes. Great for test suites, builds, deployments, or anything that takes more than a minute.
For servers/watchers, do NOT use shell-level background wrappers (nohup/disown/setsid/trailing '&') in foreground mode. Use background=true so Hermes can track lifecycle and output.
After starting a server, verify readiness with a health check or log signal, then run tests in a separate terminal() call. Avoid blind sleep loops.
Use process(action="poll") for progress checks, process(action="wait") to block until done.
Working directory: Use 'workdir' for per-command cwd.
PTY mode: Set pty=true for interactive CLI tools (Codex, Claude Code, Python REPL).

Do NOT use vim/nano/interactive tools without pty=true — they hang without a pseudo-terminal. Pipe git output to cat if it might page.

The command to execute on the VM

Run the command in the background. Two patterns: (1) Long-lived processes that never exit (servers, watchers). (2) Long-running tasks paired with notify_on_complete=true — you can keep working and get notified when the task finishes. For short commands, prefer foreground with a generous timeout instead.

Max seconds to wait (default: 180, foreground max: 600). Returns INSTANTLY when command finishes — set high for long tasks, you won't wait unnecessarily. Foreground timeout above 600s is rejected; use background=true for longer commands.

Working directory for this command (absolute path). Defaults to the session working directory.

Run in pseudo-terminal (PTY) mode for interactive CLI tools like Codex, Claude Code, or Python REPL. Only works with local and SSH backends. Default: false.

When true (and background=true), you'll be automatically notified exactly once when the process finishes. **This is the right choice for almost every long-running task** — tests, builds, deployments, multi-item batch jobs, anything that takes over a minute and has a defined end. Use this and keep working on other things; the system notifies you on exit. MUTUALLY EXCLUSIVE with watch_patterns — when both are set, watch_patterns is dropped.

Strings to watch for in background process output. HARD RATE LIMIT: at most 1 notification per 15 seconds per process — matches arriving inside the cooldown are dropped. After 3 consecutive 15-second windows with dropped matches, watch_patterns is automatically disabled for that process and promoted to notify_on_complete behavior (one notification on exit, no more mid-process spam). USE ONLY for truly rare, one-shot mid-process signals on LONG-LIVED processes that will never exit on their own — e.g. ['Application startup complete'] on a server so you know when to hit its endpoint, or ['migration done'] on a daemon. DO NOT use for: (1) end-of-run markers like 'DONE'/'PASS' — use notify_on_complete instead; (2) error patterns like 'ERROR'/'Traceback' in loops or multi-item batch jobs — they fire on every iteration and you'll hit the strike limit fast; (3) anything you'd ever combine with notify_on_complete. When in doubt, choose notify_on_complete. MUTUALLY EXCLUSIVE with notify_on_complete — set one, not both.

Convert text to speech audio. Returns a MEDIA: path that the platform delivers as native audio. Compatible providers render as a voice bubble on Telegram; otherwise audio is sent as a regular attachment. In CLI mode, saves to ~/voice-memos/. Voice and provider are user-configured (built-in providers like edge/openai or custom command providers under tts.providers.<name>), not model-selected.

The text to convert to speech. Provider-specific character caps apply and are enforced automatically (OpenAI 4096, xAI 15000, MiniMax 10000, ElevenLabs 5k-40k depending on model); over-long input is truncated.

Optional custom file path to save the audio. Defaults to ~/.hermes/audio_cache/<timestamp>.mp3

todo

Manage your task list for the current session. Use for complex tasks with 3+ steps or when the user provides multiple tasks. Call with no parameters to read the current list.

Writing:
- Provide 'todos' array to create/update items
- merge=false (default): replace the entire list with a fresh plan
- merge=true: update existing items by id, add any new ones

Each item: {id: string, content: string, status: pending|in_progress|completed|cancelled}
List order is priority. Only ONE item in_progress at a time.
Mark items completed immediately when done. If something fails, cancel it and add a revised item.

Always returns the full current list.

Task items to write. Omit to read current list.

Unique item identifier

Task description

Current status

true: update existing items by id, add new ones. false (default): replace the entire list.

Inspect an image from a URL, file path, or tool output when you need closer detail than what's visible in the conversation. If the user's image is already attached to the conversation and you can see it, just answer directly — only call this tool for images referenced by URL/path, images returned inside other tool results (browser screenshots, search thumbnails), or when you need a deeper look at a specific region the main model's vision may have missed.

Image URL (http/https) or local file path to analyze.

Your specific question or request about the image to resolve. The AI will automatically provide a complete image description AND answer your specific question.

Extract content from web page URLs. Returns page content in markdown format. Also works with PDF URLs (arxiv papers, documents, etc.) — pass the PDF link directly and it converts to markdown text. Pages under 5000 chars return full markdown; larger pages are LLM-summarized and capped at ~5000 chars per page. Pages over 2M chars are refused. If a URL fails or times out, use the browser tool to access it instead.

List of URLs to extract content from (max 5 URLs per call)

Search the web for information. Returns up to 5 results by default with titles, URLs, and descriptions. The query is passed through to the configured backend, so operators such as site:domain, filetype:pdf, intitle:word, -term, and "exact phrase" may work when the backend supports them.

The search query to look up on the web. You may include backend-supported operators such as site:example.com, filetype:pdf, intitle:word, -term, or "exact phrase".

Maximum number of results to return. Defaults to 5.

Write content to a file, completely replacing existing content. Use this instead of echo/cat heredoc in terminal. Creates parent directories automatically. OVERWRITES the entire file — use 'patch' for targeted edits.

Path to the file to write (will be created if it doesn't exist, overwritten if it does)

Complete content to write to the file

Retrieve or update a peer card from Honcho — a curated list of key facts about that peer (name, role, preferences, communication style, patterns). Pass `card` to update; omit `card` to read.  If the card is empty, the result includes a `hint` field explaining why (observation disabled, fresh peer, dialectic layer still warming up, etc.) — this is NOT an error.  Peer cards accumulate over time from observed conversation.

Peer to query. Built-in aliases: 'user' (default), 'ai'. Or pass any peer ID from this workspace.

New peer card as a list of fact strings. Omit to read the current card.

Semantic search over Honcho's stored context about a peer. Returns raw excerpts ranked by relevance — no LLM synthesis. Cheaper and faster than honcho_reasoning. Good when you want to find specific past facts and reason over them yourself.

What to search for in Honcho's memory.

Token budget for returned context (default 800, max 2000).

Ask Honcho a natural language question and get a synthesized answer. Uses Honcho's LLM (dialectic reasoning) — higher cost than honcho_profile or honcho_search. Can query about any peer via alias or explicit peer ID. Pass reasoning_level to control depth: minimal (fast/cheap), low (default), medium, high, max (deep/expensive). Omit for configured default.

A natural language question.

Override the default reasoning depth. Omit to use the configured default (typically low). Guide:
- minimal: quick factual lookups (name, role, simple preference)
- low: straightforward questions with clear answers
- medium: multi-aspect questions requiring synthesis across observations
- high: complex behavioral patterns, contradictions, deep analysis
- max: thorough audit-level analysis, leave no stone unturned

Retrieve full session context from Honcho — summary, peer representation, peer card, and recent messages. No LLM synthesis. Cheaper than honcho_reasoning. Use this to see what Honcho knows about the current conversation and the specified peer.

Optional focus query to filter context. Omit for full session context snapshot.

Write or delete a conclusion about a peer in Honcho's memory. Conclusions are persistent facts that build a peer's profile. You MUST pass exactly one of: `conclusion` (to create) or `delete_id` (to delete). Passing neither is an error. Deletion is only for PII removal — Honcho self-heals incorrect conclusions over time.

A factual statement to persist. Provide this when creating a conclusion. Do not send it together with delete_id.

Conclusion ID to delete for PII removal. Provide this when deleting a conclusion. Do not send it together with conclusion.


[The user sent an image~ Here's what I can see:
Here is a detailed description of the image:

**Overall Impression:**
The image shows a close-up of a door, likely an interior door, with a hole drilled for a doorknob and a mortise cut for the latch plate. The door appears to be in the process of being installed or repaired. The background features a tiled wall.

**Door Details:**

*   **Color and Finish:** The door is painted in a light, muted color, possibly a light gray or off-white. The paint has a slightly textured finish, revealing the wood grain underneath.
*   **Hole for Doorknob:** A circular hole has been drilled into the door, presumably for the doorknob mechanism. The edges of the hole are rough, showing the raw wood and some splintering.
*   **Mortise for Latch Plate:** On the edge of the door, a rectangular mortise has been cut to accommodate the latch plate. Two screws are visible, securing the latch plate in place. The wood inside the mortise is exposed and appears unfinished.
*   **Edge of Door:** The edge of the door is visible, showing the layered construction of the door. The wood grain is more prominent on the edge.

**Background Details:**

*   **Tiled Wall:** The background consists of a wall covered in white, rectangular tiles. The tiles are arranged in a horizontal pattern with visible grout lines.
*   **Color and Texture:** The tiles have a glossy finish, reflecting light. The grout lines are a slightly darker shade of white or gray.
*   **Other Details:** A small, round, white object is visible on the tiled wall, possibly a wall anchor or a decorative element.

**Lighting and Composition:**

*   **Lighting:** The lighting appears to be soft and diffused, with no harsh shadows. The light source is likely coming from the front or side of the door.
*   **Composition:** The image is tightly cropped, focusing on the door and the immediate surrounding area. The composition is simple and straightforward, emphasizing the details of the door and the unfinished hardware.

**Overall, the image conveys a sense of construction, repair, or renovation. The unfinished state of the door and the exposed hardware suggest that the project is still in progress.**]
[If you need a closer look, use vision_analyze with image_url: /home/ubuntu/.hermes/image_cache/img_819598d874b1.jpeg ~]

[The user sent an image~ Here's what I can see:
Here is a detailed description of the image:

**Overall Impression:**

The image is a close-up shot of a door and its hardware. The focus is on the door handle, lock mechanism, and a set of keys hanging from the handle. The lighting is soft and diffused, creating subtle shadows and highlights on the surfaces.

**Door and Surface:**

*   **Color:** The door appears to be painted in a light, neutral color, possibly off-white or a very pale beige.
*   **Texture:** The door has a subtle vertical wood grain texture, indicating it is likely made of wood or a wood composite material.
*   **Condition:** The door appears to be in good condition, with no visible major scratches or damage.

**Door Hardware:**

*   **Door Handle:** The door handle is made of a brushed metal, likely stainless steel or a similar alloy. It has a cylindrical shape with a rounded end. A key is inserted into the handle.
*   **Escutcheon Plate:** The door handle is mounted on a circular escutcheon plate, also made of the same brushed metal.
*   **Strike Plate:** On the door frame, there is a strike plate, which is the metal plate that the door latch engages with. It is secured with two screws. The strike plate appears to be slightly worn or tarnished.
*   **Latch:** The latch mechanism is visible, protruding from the door edge.

**Keys:**

*   **Keys:** A set of two keys hangs from a metal ring attached to the door handle. The keys are silver in color and appear to be standard pin tumbler keys.
*   **Key Ring:** The keys are attached to a simple metal key ring.

**Composition and Lighting:**

*   **Angle:** The image is taken at a slight angle, providing a clear view of the door handle, keys, and strike plate.
*   **Lighting:** The lighting is soft and even, with subtle shadows that define the shapes and textures of the objects. There are no harsh highlights or deep shadows.

**Overall Impression:**

The image is a simple and straightforward depiction of a door and its hardware. The focus is on the functional elements of the door, such as the handle, lock, and keys. The neutral color palette and soft lighting create a calm and understated aesthetic.]
[If you need a closer look, use vision_analyze with image_url: /home/ubuntu/.hermes/image_cache/img_15abb82e3d47.jpeg ~]

[The user sent an image~ Here's what I can see:
Here's a detailed description of the image:

**Overall Impression:**

The image shows a close-up of a door with a metal door handle and keys inserted. The door appears to be painted a light color, and the lighting creates shadows that add depth to the scene.

**Door:**

*   **Color:** The door is painted in a light color, possibly off-white or a very pale beige.
*   **Texture:** The door has a textured surface, with visible vertical lines or grooves. This suggests it might be a painted wooden door with a grain pattern or a textured paint finish.
*   **Details:** The edge of the door is visible on the left side of the frame, showing the thickness of the door. A metal strike plate is visible on the door edge.

**Door Handle:**

*   **Material:** The door handle appears to be made of brushed metal, likely stainless steel or a similar alloy.
*   **Design:** It's a lever-style handle with a cylindrical grip. The base of the handle is a circular plate that is mounted flush against the door.
*   **Condition:** The handle looks clean and well-maintained.

**Keys:**

*   **Quantity:** There are two keys hanging from a metal keyring.
*   **Material:** The keys are made of metal, matching the door handle in color and finish.
*   **Position:** The keys are inserted into the keyhole of the door handle, hanging downwards.

**Shadows:**

*   **Direction:** The shadows cast by the door handle and keys indicate that the light source is coming from the upper left of the frame.
*   **Intensity:** The shadows are soft and diffused, suggesting a relatively soft or indirect light source.

**Composition:**

*   The door handle and keys are the central focus of the image.
*   The composition is simple and clean, with the door providing a neutral background.
*   The angle of the shot is slightly off-center, which adds visual interest.]
[If you need a closer look, use vision_analyze with image_url: /home/ubuntu/.hermes/image_cache/img_f41cc77b052a.jpeg ~]

[nachlakes] se rompió la cerradura de la puerta del baño necesito que me busques una igual en mercadolibre.


Explanation:
**Searching for options**

I think I need to search for machine learning resources, maybe focusing on something related to vision. I’m considering using a web search, possibly looking at an Argentine site for relevant information. If I'm having trouble finding anything, I might use vision analysis to identify something else that could help. It seems like I'm trying to connect all these tools to get the best results for what I need. Let's see how this goes!

Question: Identify the door lock/handle type and visible characteristics needed to find an equivalent replacement in Argentina/MercadoLibre. Focus on whether it is a bathroom/privacy lock, lever rosette type, finish, key/cylinder style, and likely search terms.


Here's a breakdown of the image and how to find a replacement lock in Argentina:

**Image Description**

The image shows a door with a lever-style door handle. Key features:

*   **Door:** The door appears to be a standard interior door, likely made of wood or a composite material, and painted white.
*   **Door Handle:** The handle is a lever type, meaning it's operated by pushing down on a lever rather than turning a knob.
*   **Rosette:** The handle is mounted on a circular rosette (the round plate behind the lever).
*   **Finish:** The finish appears to be brushed nickel or satin chrome. It has a matte, slightly textured appearance.
*   **Lock Type:** The handle has a key cylinder visible, indicating it's a keyed entry lock. This means it can be locked and unlocked from both sides using a key.
*   **Strike Plate:** The strike plate (the metal plate on the door frame where the latch bolt engages) is visible. It's a standard rectangular shape.
*   **Key:** A standard pin tumbler key is hanging from the lever.

**Identifying a Replacement in Argentina/MercadoLibre**

Here's how to find a suitable replacement, focusing on the key characteristics:

1.  **Lock Type:** This is a keyed entry lever lock. You'll need to search for a lock that provides security and can be locked/unlocked with a key from both sides.

2.  **Lever Style and Rosette:** The lever is a simple, cylindrical design. The rosette is circular and relatively plain. When searching, look for similar lever styles and rosette shapes to match the existing aesthetic.

3.  **Finish:** The finish is brushed nickel or satin chrome. This is a common finish, so it shouldn't be too difficult to find.

4.  **Key/Cylinder Style:** The key is a standard pin tumbler key. This is the most common type of key, so any keyed entry lever lock should come with a compatible cylinder.

5.  **Backset:** The backset is the distance from the edge of the door to the center of the bore hole for the handle. This is a critical measurement. You'll need to measure the backset of your existing lock to ensure the replacement will fit. Standard backsets are typically 60mm or 70mm.

6.  **Door Thickness:** Door thickness is also important. Standard doors are typically 35mm to 45mm thick. The lock you choose must be compatible with your door's thickness.

**Likely Search Terms for MercadoLibre Argentina:**

Here are some search terms you could use on MercadoLibre Argentina:

*   "Cerradura manija puerta entrada" (Entry door handle lock)
*   "Cerradura manija palanca puerta" (Lever door handle lock)
*   "Cerradura puerta llave" (Door lock with key)
*   "Manija puerta acero inoxidable" (Stainless steel door handle) - if you want to emphasize the material
*   "Cerradura manija redonda" (Round handle lock) - to emphasize the rosette shape
*   "Cerradura puerta entrada niquel satinado" (Satin nickel entry door lock) - to emphasize the finish

**Additional Tips:**

*   **Measure Everything:** Before searching, carefully measure the backset, door thickness, and the diameter of the rosette.
*   **Read Descriptions Carefully:** Pay close attention to the product descriptions on MercadoLibre. Make sure the lock is a keyed entry lock and that the dimensions are compatible with your door.
*   **Check Reviews:** Read reviews from other buyers to get an idea of the quality and reliability of the lock.
*   **Consider a Set:** If you're replacing multiple locks, consider buying a set to ensure they all have the same key.
*   **Consult a Locksmith:** If you're unsure about which lock to choose, consult a local locksmith. They can help you select the right lock for your needs and install it properly.

By focusing on these key characteristics and using the appropriate search terms, you should be able to find a suitable replacement door lock on MercadoLibre Argentina.


Question: Look at the latch/door edge and bore. Identify if this is a tubular/cylindrical lockset, approximate backset, latch faceplate shape/dimensions, and any detail relevant for buying a compatible MercadoLibre replacement.


Okay, let's analyze the image and address the questions about the lockset.

**Image Description:**

The image shows a section of a door, likely an interior door, with the lockset removed. The door is painted a light color, possibly white or a light gray, and has a visible wood grain texture.  We can see the two holes where the lockset was installed: a larger circular bore on the face of the door for the knob/lever mechanism, and a smaller mortise on the door's edge for the latch bolt and faceplate.  The background shows white subway tiles, suggesting this is a bathroom or kitchen.

**Lockset Analysis:**

Based on the image, here's what we can determine about the lockset:

*   **Type:** This is almost certainly a **tubular/cylindrical lockset**. The large circular bore on the door face is characteristic of this type of lock. Tubular locksets are the most common type found in residential interior doors.

*   **Backset:** The backset is the distance from the edge of the door to the center of the bore hole.  Visually estimating from the image, the backset appears to be a **standard 2 3/8 inches (60mm)**. This is the most common backset size. It could potentially be 2 3/4 inches (70mm), but 2 3/8" is more likely.

*   **Latch Faceplate Shape/Dimensions:** The latch faceplate is the metal plate that sits flush with the door edge and surrounds the latch bolt. From the image, we can see:

    *   **Shape:** The faceplate is **rounded corner**.
    *   **Dimensions:** It's difficult to give exact dimensions without a ruler, but we can estimate. A standard latch faceplate is approximately 2 1/4 inches (57mm) tall and 1 inch (25mm) wide.

*   **Relevant Details for MercadoLibre Replacement:**

    To find a compatible replacement on MercadoLibre, you'll need to consider the following:

    1.  **Backset:**  Specify "2 3/8 inch backset" or "60mm backset" in your search.
    2.  **Latch Faceplate Shape:** Specify "rounded corner latch faceplate".
    3.  **Latch Faceplate Dimensions:** While not always listed, it's helpful to know the approximate dimensions (2 1/4" x 1") to ensure a good fit.
    4.  **Door Thickness:**  Locksets are designed for specific door thicknesses. Measure the thickness of your door and ensure the replacement lockset is compatible. Standard door thicknesses are 1 3/8 inches or 1 3/4 inches.
    5.  **Function:** Determine the function of the lockset you need (passage, privacy, entry). Passage locksets don't have a locking mechanism, privacy locksets have a button or turn piece on the inside, and entry locksets have a key cylinder.
    6.  **Finish:** Choose a finish that matches your existing hardware (e.g., brushed nickel, polished brass, matte black).
    7.  **Bore Hole Diameter:** While not visible in the image, measure the diameter of the bore hole on the door face to ensure the new lockset will fit. Standard bore hole diameters are 2 1/8 inches.

**In summary, when searching on MercadoLibre, use keywords like:**

"Cerradura tubular 60mm backset" (Tubular lock 60mm backset)
"Cerradura para puerta interior" (Interior door lock)
"Placa de pestillo esquina redonda" (Rounded corner latch plate)

Remember to double-check all measurements and specifications before purchasing to ensure compatibility.


Question: site:mercadolibre.com.ar cerradura tubular manija palanca roseta redonda llave baño acero inoxidable 60mm


Contrafrente acero inoxidable cerradura

Contrafrente Acero Inoxidable Cerradura | Mercado
[...]
**0 productos en tu carrito
* Búsquedas relacionadas
* remaches acero inoxidable
* mesada acero inoxidable 150
* chapa perforada acero inoxidable
* chapa acero inoxidable materiales
* tablero electrico acero inoxidable
* manijones de acero inoxidable para puertas
* bisagras para puertas vaiven acero inoxidable
# Contrafrente acero inoxidable cerradura
196 resultados
Saltar a resultados
Filtros
[...]
* te ahorra envíosCon tu carrito de compras
* Miles de productos del mundo a tu casa
*
[...]
Promocionado
[...]
3. Cerradura Kallay 503 Frente Acero Inoxidable Ref Puerta
MÁS VENDIDOKALLAY### Cerradura Kallay 503 Frente Acero Inoxidable Ref Puerta
Calificación 4,4 de 5 (253 calificaciones)4.4(253)
~~$9.300~~
$8.5568% OFF
en6 cuotas de$1.958
Llega hoy
Otra opción de compra
$10.776
Mismo precio en 3 cuotas de$3.592

4. Cerradura externa de acero inoxidable hafele
HÄFELE### Cerradura externa de acero inoxidable hafele
$58.950
en6 cuotas de$13.490
Llega gratis hoy
[...]
5. BRONZEN### Cerrojo Libre-ocupado De Aplicar - Acero Inox Para Baño
Por HERRAJES PATRICIOS
Calificación 4,6 de 5 (20 calificaciones)4.6(20)
$21.418
en6 cuotas de$4.901
Llega hoy
[...]
6. ### Cerradura P/ Puerta Blindex Premium Acero Inox
Por QBO
Calificación 4,5 de 5 (2 calificaciones)4.5(2)
$30.952
en6 cuotas de$7.083
Llega hoy
Enviado por
[...]
7. ### Cerradura Acero Inox. Baulera Carrocería Gabinete Armario
Calificación 5 de 5 (1 calificaciones)5.0(1)
$39.673
en6 cuotas de$9.079
Envío gratis
[...]
8. KALLAY### Cerradura Exterior Kallay 3001 Frente Inoxidable Color Acero Inoxidable
Calificación 3,7 de 5 (3 calificaciones)3.7(3)
~~$24.990~~
$19.22223% OFF
en6 cuotas de$4.399
Llega hoy
Enviado por
Otra opción de compra
[...]
~~$29.990~~
[...]
$24.46718% OFF
[...]
Mismo precio en
[...]
3 cuotas de$8.155
[...]
* ### Cerradura Reforzada Con Frente Inoxidable Para Eurocilindro
[...]
Por QBO
[...]
* ### Cerradura Cerrojo Puerta Vidrio Blindex Acero Inoxidable+acc
[...]
Calificación 5 de 5 (2 calificaciones)5.0(2)
[...]
* KALLAY### Cerradura Kallay 504 Frente Ancho Acero Inoxidable Reforzada
$12.933
en6 cuotas de$2.959
Llega hoy
[...]
Otra opción de compra
[...]
$16.398
[...]
Mismo precio en 3 cuotas de$5.466
[...]
* ### Cerradura Acero Inox. Armarios Gabinete Baulera Carrocería
$39.500
en6 cuotas de$9.039
Envío gratis
[...]
* ### Cerradura P/ Puerta Blindex Premium Acero Inoxidable
Por QBO
Calificación 5 de 5 (4 calificaciones)5.0(4)
$30.952
en6 cuotas de$7.083
[...]
* KALLAY### Cerradura Kallay 504 Frente Ancho Acero Inoxidable Reforzada
$16.398
Mismo precio en 3 cuotas de$5.466
[...]
* ### Cerradura Pomo Para Oficina Con Llave Y Boton Acero Inox
[...]
* ### Cerradura Abc 1120 Simil Acytra 6005 Trabex 1020 Kallay 4005 Prive 207
Por Sudineroseguro
Calificación 4,8 de 5 (13 calificaciones)4.8(13)
$17.499
Mismo precio en 6 cuotas de$2.916
Llega hoy
[...]
Otra opción de compra
[...]
$17.499
Mismo precio en 6 cuotas de$2.916
[...]
* ### Número Acero Inoxidable 25 Cm Dirección Frente De Casa Color Inox
[...]
Por HERRAJES TUYU
[...]
$15.113
[...]
en6 cuotas de$3.458
[...]
Llega hoy
[...]
* KALLAY### Cerradura Kallay 503 Frente Acero Inoxidable Puerta
Por HERRAJES VEIGA
$9.600
en6 cuotas de$2.196
Llega hoy
[...]
* ### Cerrojo Cerradura Puerta Blindex A Pared 3 Llaves+ Accesorio
[...]
$24.996
[...]
Enviado por
[...]
* RECOMENDADO### Cerradura Para Puerta De Vidrio Blindex Montante Inomax IM8006 Acero Inoxidable no Requiere Perforación 3 Llaves
Por Inomax
Calificación 4,5 de 5 (19 calificaciones)4.5(19)
$17.384
en6 cuotas de$3.978
Llega hoy
[...]
Enviado por
[...]
* ### Inomax Pomo Cerradura Pomo Con Llave Y Botón Acero Inoxidable
[...]
Por Inomax
[...]
Calificación 4,6 de 5 (55 calificaciones)4.6(55)
[...]
* KALLAY### Cerradura Interior Kallay 503 Pta. Redonda Frente Inoxidable
Calificación 4,6 de 5 (14 calificaciones)4.6(14)
~~$11.990~~
$9.83118% OFF
en6 cuotas de$2.250
Llega hoy
[...]
Enviado por

Cerradura llavin

Cerradura Llavin | Mercado
[...]
# Cerradura llavin
59 resultados
Saltar a resultados
[...]
Resultados
Ordenar por
Más relevantes
1. Llavin Para Cerradura De Baño Bronce Platil
### Llavin Para Cerradura De Baño Bronce Platil
~~$5.000~~
$4.6008% OFF
Llega mañana
Calificación 5 de 5 (1 calificaciones)5.0(1)
[...]
Promocionado
2. Cerradura Llavin Para Baño Libre Ocupado Acero Inox
### Cerradura Llavin Para Baño Libre Ocupado Acero Inox
$13.590
Llega gratis mañana
Calificación 5 de 5 (2 calificaciones)5.0(2)
[...]
Promocionado
[...]
### Llavin Perilla Para Baño Libre Ocupado Acero Inox Bronzen
[...]
4. BRONZEN### Pomo Para Baño Libre Ocupado Acero Inoxidable Para Cerradura Acero Inoxidable
$11.250
[...]
Llega mañana
[...]
5. MÁS VENDIDOBRONZEN### Cerrojo De Baño Con Llavin Zincado 50mm Acero Inoxidable
Por Keuken
~~$8.937~~
$8.04310% OFF
[...]
Llega mañana
[...]
.5(2)
[...]
7. ### Llavin Cerrojo Para Baño De Aplicar Redondo Acero Negro
$13.341
[...]
Llega mañana
[...]
8. ### Pomo De Baño Llavín Con Bocallave - Acero Inoxidable
[...]
9. ### Llavin Para Cerradura De Baño Bronce Platil
$5.300
Calificación 5 de 5 (4 calificaciones)5.0(4)
[...]
10. ### Pomo Libre Ocupado Cerradura Baño Llavin Traba Cerratex
$4.147
[...]
Disponible 3 días después de tu compra
[...]
### Llavin Perilla Bronzen Para Baño Libre Ocupado Acero Inox Color Plateado
[...]
12. ### Llave Llavín Solo De Emergencia Para Libre Ocupado Baño
$8.608
[...]
Llega mañana
[...]
Enviado por
[...]
13. ### Llavin Para Cerradura De Baño Bronce Platil
~~$5.000~~
$4.6008% OFF
Llega mañana
Calificación 5 de 5 (1 calificaciones)5.0(1)
[...]
14. KALLAY### Cerradura De Baño Puerta Con Llavin Libre/ocupado Kallay 505
Por ALLSUR HERRAJES
$21.030
[...]
Llega mañana
[...]
15. ### Cerradura Llavin Para Baño Libre Ocupado Acero Inox X 10 Uni
Por MUNDO CIMA
~~$81.847~~
$73.66210% OFF
en6 cuotas de$16.857
[...]
Llega gratis mañana
[...]
18. ### Cerradura Pomo Llavín Y Botón De Madera Con Pequeña Falla
[...]
$10.000
[...]
19. ### Cerradura Pomo Llavín Para Baño Negro Perilla Puerta Cima M
[...]
20. ### Llavin Perilla Bronzen Para Baño Acero Inox
[...]
$9.486
[...]
### Cerradura Pomo Dorada Con Llavín Y Botón Con Pequeña Falla Dorado
[...]
### Llavin Perilla Bronzen Para Baño Acero Inox
[...]
23. KALLAY### Cerradura Puerta De Baño + Llavin Libre/ocupada Kallay 506
Por ALLSUR HERRAJES
$23.324
[...]
24. ### Cerradura Llavin Para Baño Libre Ocupado Acero Inox Cima M
Por MUNDO CIMA
~~$9.584~~
$8.62510% OFF
Llega mañana
Calificación 5 de 5 (1 calificaciones)5.0(1)
[...]
ZEN### Cerrojo De Baño Con Llavin Inox Satinado 50mm Premium
[...]
### Llavin
[...]
### Llavin
[...]
illa Bronzen Para Baño Libre Ocupado Acero Inox
[...]
28. ### Cerradura Tipo Pomo Con Llavín Y Botón Con Pequeña Falla
[...]
29. ### Cerradura Pomo Llavín Para Baño Negro Perilla Pack X 4 Uni
[...]
31. ### Cerradura Llavin Para Baño Libre Ocupado Acero Inox
$13.590
Llega gratis mañana
Calificación 5 de 5 (2 calificaciones)5.0(2)
[...]
33. ### Cerradura Llavin Para Baño Libre Ocupado Acero Inox X 4 Uni
Por MUNDO CIMA
~~$32.738~~
$29.46410% OFF
[...]
Llega mañana
[...]
34. ### Cerradura Pomo Llavín Baño Perilla Puerta Acero Cepillado
[...]
### Cerradura Pomo Pfw Bolita Acero Inox - Simple Llavín Y Botón
[...]
36. ### Cerradura Para Baño Kallay 505 + Llavin Libre Ocupado Currao
$24.500
[...]
Disponible 3 días después de tu compra
[...]
### Cerradura Pomo Dorada Llavín Y Botón Con
[...]
### Cerradura Pomo Color Madera Y Plateado Con Llavín Y Botón Madera Con Plateado
[...]
40. KALLAY### Cerradura Para Puerta D Baño + Llavin + Picaporte Kallay 506
Por ALLSUR HERRAJES
$33.783
[...]
44. ### Llave Para Cierre Gabinete De Gas O Cerradura Baño - M Moya
[...]
$3.250
[...]
46. ### Tambor Llavín Cerradura Traba Ktm Duke 200 3ra Gen 2024-2025
[...]
48. ### Cerradura Casilla Gas Con Llavin
[...]
50. ### Llave Llavin Cerradura Cierre Casilla De Gas X 3 Unidades

Cerradura bano abierto cerrado puerta

Cerradura Bano
[...]
# Cerradura bano abierto cerrado puerta
130 resultados
Saltar a resultadosFiltros
* Llegan hoy
* te da envío gratisEn carritos desde $ 33.000
* Miles de productos del mundo a tu casa
* Envío gratis
### Ti
[...]
* Kallay(13)
* Bronzen(10)
* Gadnic(7)
* Trabex(6)
* Genérica(5)
* Currao(4)
* Nogoyá(4)
* Cerratex(4)
* Kwikset(3)
* Mostrar más
[...]
### Acabado
[...]
* Satinado(24)
* Cromado(11)
* Niquelado(8)
* Zincado(8)
* Acero inoxidable(3)
* Cromo(2)
* Negro/Mate(1)
* Plateado(1)
* Níquel(1)
* Mostrar más
[...]
### Lugar de colocación
[...]
* Puerta(85)
[...]
### Materiales de la cerradura
* Acero(35)
* Hierro(7)
* Acero inoxidable(5)
* Metal(2)
* Zamak(1)
* Bronce(1)
[...]
### Tipo de cerradura
[...]
* Unidireccional(36)
[...]
### Tipo de apertura
[...]
* Abatible(58)
* Corrediza(4)
* Batiente(2)
* Manual(2)
* Rebatible(1)
[...]
6. ### Cerradura Libre/ocupado De Aplicar Baño Acero Inoxidable
$
[...]
* ### Cerradura Cerratex 4000 Simil Acytra 101, Candex 118,
[...]
### Cerradura Para Pu
[...]
* BRONZEN### Cerradura Magnetica Puerta De Baño Frente Acero Inox
[...]
Cerradura Ba
[...]
* KALLAY### Cerradura Baño/dormitorio Kallay 505 Pta. Redonda Fte Inox.
Calificación 4,3 de 5 (3 calificaciones)4.3(3)
~~$13.490~~
$11.46615% OFF
Llega mañana
[...]
* TRABEX### Cerradura Trabex 1005 Puerta Placa Int. Reversible Baño 505 Color Zincada
[...]
Por GRAMABI
[...]
Calificación
[...]
5 (6
[...]
)5.0(6)
[...]
~~$1
[...]
adura Kallay
[...]
Para Baño
[...]
### Cerradura Universal Con Leva A Rosca Embutir Diametro 18mm
[...]
* ### Cerradura Currao 23 Hr Baño Milord Angosta Punta Redonda
[...]
Por HERRAJ
[...]
3(32)
[...]
* KALLAY### Cerradura De Baño Kallay 505 Traba + Picaporte Manija Toshi
[...]
rao Baño
[...]
Redondas
[...]
### Cerradura Universal Con Leva A
[...]
etro 18mm
[...]
* KALLAY### Cerradura Kallay 505 P/puerta Baño Con Perilla Libre Ocupado
[...]
Calificación
[...]
6 de 5 (
[...]
* ### Cerradura De Baño Kallay 505 Mas Traba Y Manija Toshi Oferta
[...]
Por HERRAJES VEIGA
[...]
Calificación 4,7 de
[...]
calificaciones)4
[...]
7(8
[...]
* ### Cerradura Currao De Baño Art.98hc De Mano Derecha
[...]
* ### Palanca De Entrada De Entrada Con Llave De Brotima 2 Paquete
~~$402.606~~
$374.4127% OFF
Mismo precio en 1 cuotas de$374.412
Envío gratis
[...]
* ### Cerrojo Baño Terra Aluminio Acerado Puerta 50 Mm Cerradura
Por HERRAJES TUYU
Calificación 4 de 5 (2 calificaciones)4.0(2)
$10.480
[...]
Llega mañana
[...]
* BRONZEN### Cerradura Libre/ocupado De Aplicar Baño Puerta Placa

Manija y cerraduras para puertas

* Búsquedas relacionadas
* manijas para portones
* picaportes para puertas
* cubetas para puertas corredizas
* manijas para puertas antiguas y
* picaportes para puerta exterior
* manijas para puertas de entrada
* herrajes para puertas corredizas
# Manija y cerraduras para puertas
1.288 resultados
Saltar a resultados
[...]
Cerradura Abc 1125 Simil Acytra 6006 Trabex 1025 Kallay 4006 Prive 208
[...]
Resultados
Ordenar por
Más relevantesMás relevantes
1. Cerradura De Baño Kallay 505 Mas Traba Y Manija Toshi Oferta
### Cerradura De Baño Kallay 505 Mas Traba Y Manija Toshi Oferta
Por HERRAJES VEIGA
~~$44.809~~
$30.42632% OFF
en6 cuotas de$6.962
[...]
Llega mañana
[...]
Calificación 4,6 de 5 (79 calificaciones)4.6(79)
[...]
Promocionado
[...]
2. Manija Porton Exterior Con Cerradura S10 1996 2001 2008 2011
### Manija Porton Exterior Con Cerradura S10 1996 2001 2008 2011
[...]
$33.545
[...]
en6 cuotas de$7.676
[...]
Envío gratis
[...]
3. ### Manija Con Cerradura Exterior Para Cupula
[...]
$58.800
[...]
en6 cuotas de$13.456
[...]
Llega gratis mañana
[...]
Enviado por
[...]
Calificación 4,5 de 5 (45 calificaciones)4.5(45)
[...]
4. JAQUE### Acceso Exterior Jaque Pomo O Manija Antipánico C/ Llave
Por HERRAJES VEIGA
$58.313
en6 cuotas de$13.344
[...]
Llega gratis mañana
[...]
5. ### Cerradura De Baño Kallay 505 Mas Traba Y Manija Toshi Oferta
[...]
Por HERRAJES VEIGA
[...]
~~$44.809~~
$30.42632% OFF
[...]
en6 cuotas de$6.962
[...]
Llega mañana
[...]
IDO### Manija Porton Exterior Con Cerradura S10 1996 2001 2008 2011
[...]
### Combo N 1 Cerradura Puerta Placa Manija Ministerio Aluminio
[...]
Acceso Llave Man
[...]
### Combo N14 Cerradura Puerta Placa Manija Biselada Aluminio
[...]
17. ### Manija Puerta Doble Balancín Inox +cerradura Interior Milord
$16.665
[...]
en6 cuotas de$3.813
[...]
Llega mañana
[...]
18. ### Manija Cerradura Con Llave Tipo Jeep Motohome Casa Rodante
[...]
20. ### Cerradura Kallay 503 + Manija Toshi Acero Puerta Interior Color Níquel
Por HERRAJES TUYU
$25.575
en6 cuotas de$5.852
[...]
Llega mañana
[...]
Calificación 5 de 5 (1 calificaciones)5.0(1)
[...]
22. JAQUE### Acceso Exterior Jaque Manija Cerradura Antipánico Llave Yale
[...]
lega gratis mañana
[...]
23. ### Combo N 4 Cerradura Puerta Placa Interior Manija Acero Inox. Esmerilado
[...]
Llega mañana
[...]
25. ### Kit Cerraduras Fiat 147 Puerta Capot Baul Manija Topes
[...]
6 Cerradura Puerta
[...]
aca Manija Biselada Alumin
[...]
31. KALLAY### Cerradura Puerta Exterior Kallay 4000 Manijon Manija Toshi
[...]
32. JAQUE### Acceso Exterior Manija Antipánico Sin Llave
[...]
Por HERRAJES PATRICIOS
[...]
34. ### Cerradura Kallay 503 Y Manija Arezzo Cromada Puerta Interior
[...]
Por HERRAJES VEIGA
[...]
~~$28.207~~
[...]
$26.7965% OFF
[...]
en6 cuotas de$6.132
[...]
Llega mañana
[...]
35. ### Combo Puerta Interior Manija + Cerradura Prive Color Plateado
[...]
37. ### Cerradura Kallay 503 Y Manija Toshi Curva Acero Interior
Por HERRAJES VEIGA
~~$44.187~~
$33.14024% OFF
en6 cuotas de$7.584
[...]
Llega gratis mañana
[...]
### Kit Cerradura Kallay 505 L
[...]
ado Manija Latina2
[...]
39. ### Cerradura Kallay 503 Y Manija Toshi Acero Puerta Interior
Por HERRAJES VEIGA
[...]
~~$38.791~~
$25.21435% OFF
en6 cuotas de$5.770
[...]
Llega mañana
[...]
40. JAQUE### Manija C/ Llave Para Sistema Antipanico Jaque
Por HERRAJES VEIGA
[...]
~~$78.586~~
$7
[...]
.6565% OFF
[...]
en6 cuotas de$17.085
[...]
Llega gratis mañana
[...]
42. ### Manija Interior Fiat Palio Ventilete Cerradura
$10.300
[...]
.357
[...]
### Manija Porton Trasero C/ Cerradura Chevrolet S-10
[...]
44. ### 1 Cerradura + 1 Manija + Llaves Puerta Gol Gacel Senda 91-94
[...]
46. KALLAY### Cerradura Puerta Exterior Kallay 4003 Manijon Manija Toshi
[...]
47. ### Manija Cerradura Tapa De Motor Con Llave Fiat 600 Nacional
[...]
48. ### Cerradura Picaporte Manija Levers Acero Inoxidable - Para Puerta Placa, Madera, Metal, Ect.
[...]
50. ### Combo N15 Cerradura Puerta Placa Manija Biselada Aluminio N

Manija Premium Doble Balancín Saturno Acero Inoxidable Plateado | Envío gratis
[...]
# Manija Premium Doble Balancín Saturno Acero Inoxidable Plateado
[...]
## Características del producto
[...]
Acabado
[...]
Dirección del picaporte o manijón
[...]
| Bronzen |
| --- |
| Moderna |
| Saturno |
| Plateado |
| Brillante |
| Izquierda/Derecha |
[...]
### Dimensiones
[...]
| 12,5 cm |
| --- |
| 4,5 cm |
[...]
Ubicación del picaporte o manijón
[...]
Accesorios incluidos
[...]
| Doble Balancín |
| --- |
| Acero inoxidable |
| Izquierda/Derecha |
| Bocallaves, Perno, Tornillos |
[...]
Manija premium doble balancin Acero inox. (Para ambos lados de la puerta) - Esta manija contiene un sistema de retroceso el cual hace que tu cerradura no se dañe con el tiempo. - Modelo: Saturno - Marca: Bronzen - Incluye: - 2 Boca Llaves - 2 Rosetas - Elementos de Fijacion - Medidas: - Alto: 4,5cm - Ancho: 12,5cm - Profundidad: 3,5cm *Imágenes a modo ilustrativo ____________________________________ Somos Herrajes Danilo, una empresa destinada a la comercialización de insumos para muebles y obras, artículos para cerrajería, herrería, ferretería y electricidad, con una trayectoria de más de 30 años al servicio del público. - UBICACIÓN: Local al público en Isidro Casanova, cerca de la vía y ruta 3. - HORARIOS: Lunes a Viernes de 09:00 a 17:00 Hs. y Sábados de 09:00 a 13:00 Hs. ____________________________________ MEDIOS DE ENVÍO: - Mercado Envíos: El método de envío clásico de la plataforma. Podes revisar el costo y el tiempo aproximado de entrega con tu código postal en la publicación (El tiempo de llegada de su producto luego de ser enviado depende exclusivamente de Mercado Envíos y no de nosotros). - Mercado Envíos Full: El producto se encuentra en un almacén de Mercado Libre, haciendo este tipo de envíos uno de los más seguros y rápidos disponibles (El tiempo de llegada de su producto luego de ser enviado depende exclusivamente de Mercado Envíos Full y no de nosotros). - Retiro por nuestra única sucursal en Isidro Casanova, cerca de la vía y ruta 3. (Esta opcion no esta incluida en nuestros Envíos Full) MEDIOS DE PAGO: - Mediante Mercado Pago, contás con diferentes formas de pago, tales como: Tarjetas de débito y crédito, transferencia, billetera virtual, Rapipago o Pago Fácil. FACTURACIÓN: - Te informamos que realizamos factura A y B. - Si deseás una factura A, te pedimos que lo informes al instante de hacer tu compra por la parte de mensajería. Caso contrario, se emitirá una factura con los datos especificados en el apartado de datos para su facturación, o una factura B a consumidor final. PREGUNTAS FRECUENTES: - ¿HAY STOCK? Sí. Te contamos que si estás viendo esta publicación es porque contamos con el stock correspondiente. Comprá con confianza. - ¿EL PRODUCTO CUENTA CON GARANTÍA? Sí. Los producto que selecciones cuentan con 30 días de garantía. - ¿PUEDO CAMBIAR MI PRODUCTO? Sí. Podés realizar el cambio de tu compra a través de Mercado Libre o por nuestro local físico. - ¿PUEDO RECIBIR MÁS DE UN ARTÍCULO EN UN MISMO PAQUETE? Sí. Con la función del carrito de compras podés elegir distintos artículos y combinarlos en un solo paquete, siempre que el producto seleccionado esté disponible para Mercado Envíos o Mercado Envíos Full. Garantía del vendedor: 10 días


Explanation:
**Searching for products**

I need to find better individual products that meet specific criteria. I'll conduct a search for "manija Saturno cerradura tubular llave" to see what options are available. It's important to ensure that I gather high-quality choices that fit what I'm looking for. I’ll focus on nailing down precise keyword searches to narrow down my results efficiently. Let’s see what I can discover!

Question: site:articulo.mercadolibre.com.ar/MLA cerradura tubular manija llave acero inoxidable puerta baño roseta redonda


Question: MercadoLibre Argentina cerradura tubular manija con llave roseta redonda acero inoxidable