News for hackers. Stuff that matters.
Re:Apideck CLI – An AI-agent interface with much lower conte... by nicoritschel on Monday March 16, 2026 @11:42AM (#47400494)
While I generally prefer CLI over MCP locally, this is bad outdated information.

The major harnesses like Claude Code + Codex have had tool search for months now.

Re:Apideck CLI – An AI-agent interface with much lower conte... by injidup on Monday March 16, 2026 @12:00PM (#47400768)
Can you explain how to take advantage. Is there any specific info from anthropic with regards to context window size and not having to care about MCP?
Re:Apideck CLI – An AI-agent interface with much lower conte... by amzil on Monday March 16, 2026 @12:03PM (#47400809)
Fair point on tool search. Claude Code and Codex do have it.

But tool search is solving the symptom, not the cause. You still pay the per-tool token cost for every tool the search returns. And you've added a search step (with its own latency and token cost) before every tool call.

With a CLI, the agent runs `--help` and gets 50-200 tokens of exactly what it needs. No search index, no ranking, no middleware. The binary is the registry.

Tool search makes MCP workable. CLIs make the search unnecessary.

Re:Apideck CLI – An AI-agent interface with much lower conte... by cruffle_duffle on Monday March 16, 2026 @03:56PM (#47404008)
Let me guess the command: [error]

Wait, better check help. is it -h? [error]

Nope? Lemme try —-help. [error]

Nope.

How about just “help” [error]

Let me search the web [tons of context and tool calls]