DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a coding agent on your own model with Raw CLI

Start a working terminal coding agent on a local or hosted model in one afternoon.

Authorization notice. Raw CLI is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer who wants a coding assistant that runs on a model they choose, after trying hosted tools and wanting control over tools and the model.

The problemWriting an agent loop with file editing, shell access and saved sessions from scratch takes time before the first useful answer.

The outcomeA configured agent that reads files, edits code, runs commands and answers questions about a repository from the terminal.

What you need first

  • Node.js 22.13+ on macOS, Linux or Windows 10/11
  • Bash for the bash tool (Git Bash on Windows, or PowerShell if Bash is absent)
  • A local model served over an OpenAI-compatible endpoint, or a hosted model with an API key
  • Comfort editing a strict JSON config file

Steps

  1. Run npm install -g @tlelabs/raw.
  2. Run raw config init to create the config file.
  3. Edit the config so the local model model_id matches your installed model, or add your hosted model with api_key_env.
  4. Run raw --agent raw "Explain the tests in this repository" from the project folder.
  5. Run raw alone to open the saved REPL and continue the work.

Prompt for your agent

Install the Raw agent harness from the repo lploc94/raw-cli, set up a configured agent on the model <model-id> at <base-url>, and run it with the task "Explain the tests in <repo-path>". Expected output: a plain-text explanation of the test files. Verify that the run finished with a model answer and no configuration error.

Caveat. Tool calls run automatically with your OS account's full permissions, and cwd is not a sandbox, so add tools.rules for risky commands before pointing the agent at sensitive folders.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page