Pseudo-CLI

Client

A terminal-style shell in the browser. It does not run a real OS shell. open jumps to full tool pages (same JS as the GUI). Lightweight echo, b64, and hash run inline here with crypto-js where noted.

What this pseudo-CLI is for

Use it to experiment with Toolcore catalog ids and URL prefill patterns before wiring an assistant, bookmark, or automation note. It is a navigation and demo surface for the same public tool pages, not a hidden conversion endpoint and not a replacement for your local terminal.

Pseudo-CLI

Non-AIGC pseudo-CLI — type `help`. Same URL rules as /mcp-tools.json: `open <id>`, optional `-q`, or `--params-json` (last) for complex prefills. You may also type a catalog id as the first word (shortcut to `open`).

Nearby workflows on Toolcore

Common use cases

  • Jump from automation or agent scripts to a real tool page with the same query prefill the GUI uses.
  • Run small echo, Base64, or hash helpers without leaving the terminal metaphor.
  • Try manifest-style `open` commands when integrating with `/agent-tools.json` contracts.
  • Demonstrate how a human-in-the-loop assistant can hand off data to a browser tool instead of doing every transform inside chat.

Common mistakes to avoid

  • Expecting POSIX shell behavior

    This is a browser sandbox. It does not execute system binaries, pipes to the OS, or access your files.

  • Assuming it exposes a private API

    The open command builds normal public URLs. For deterministic server operations, use only the documented agent API capabilities.

  • Pasting secrets into examples

    Even local helpers should use redacted samples. Treat copied commands as shareable notes and avoid real tokens, keys, or customer data.

FAQ

Does anything run on Toolcore servers?

Navigation and hashing run in your tab. Opening a tool loads the normal static page—no private transform API.

Can it read files or run shell scripts?

No. It is intentionally limited to browser-side commands and navigation. It cannot access your filesystem, run binaries, or pipe output to local programs.

Why use this instead of the normal catalog?

Use the catalog for browsing. Use the pseudo-CLI when you want to test exact ids, query parameters, and manifest-style handoffs.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • browser pseudo cli
  • command-style tool launcher

More tools

Related utilities you can open in another tab—mostly client-side.