DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to use Maki: what you can do with it

What is Maki? maki is a terminal AI coding agent built to use as few context tokens as possible while staying fast and pleasant to use. It parses code with tree-sitter to read file skeletons, runs tools from a sandboxed interpreter, and lets subagents pick a weak, medium or strong model. It is written in Rust with a 60 FPS TUI, Lua plugins like neovim, and supports many providers including Ollama and llama.cpp.

How do I use it? Download the installer with curl -fsSL https://maki.sh/install.sh -o install.sh and read it with cat install.sh; then run it with chmod +x install.sh && sh install.sh, or use brew install maki; set your provider key, for example OPENAI_API_KEY or GEMINI_API_KEY. Full steps below.

2 people shared what they built with Maki. See what people are building

Trended earlier

View repo on GitHub

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer

3 use cases

What people are building with Maki

  • Benchmarkthe web

    Ran Maki, Pi and OpenCode on one local 30B model and found Maki gave the strongest repo review at 43K context

    Same prompt, model and llama.cpp server on a 128 GB Strix Halo box: Maki took 511 seconds and 53 tool calls but peaked at 43.1K context thanks to indexed search and bounded reads, against 90.6K for OpenCode, and produced the strongest review, with Pi a close second.

    Maki on GitHubTry it: Run a coding agent on your own Ollama or llama.cpp server

    By Piotr Karbowski (linkedin.com) on the web

    View original post on the web

  • Hands-onGitHub

    Used Maki with a local Qwen 27B in Ollama to rebase a GitLab patch and hit indentation errors Pi did not

    A user gave Maki, with rtk and qwen3 27b on Ollama, the task of rebasing a Rails patch from GitLab 18.x to 19.x. Repeated runs produced wrong indentation while Pi with the same model got it right; later runs without rtk were mixed but the problem still appeared.

    Maki on GitHub

    By @yuyuyureka on GitHub

    View original post on GitHub

Real builds shared on X, Hacker News, Reddit, DEV and GitHub, summed up by Deduped from each post and its links; each card links to the original post. See what people are building with other repos

Quick start with Maki

  1. Check you have what it needs: Linux, macOS or Windows; An API key or sign-in for a supported provider, or a local Ollama or llama.cpp server; Optional: rtk installed for smaller bash output.
  2. Open tontinton/maki on GitHub and read the README and license.
  3. Download the installer with curl -fsSL https://maki.sh/install.sh -o install.sh and read it with cat install.sh
  4. Run it with chmod +x install.sh && sh install.sh, or use brew install maki
  5. Set your provider key, for example OPENAI_API_KEY or GEMINI_API_KEY
  6. Start Maki in your project and give it a task; watch the index tool read skeletons before full files

These steps come from our top use case, Install Maki and cut the tokens your coding agent spends, which also has a copy-paste agent prompt.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for tontinton/maki

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Best AI repos for Software and DevOps

About this repo

  • Who it is forDevelopers who pay per token or run local models and want a fast coding agent that does not waste context.
  • Why it is hot1.3k stars, talked about in 3 AI sources we track
  • LanguageRust
  • Sourcegithub.com/tontinton/maki ยท Back to Hot repos

Requirements

  • Linux, macOS or Windows
  • An API key or sign-in for a supported provider, or a local Ollama or llama.cpp server
  • Optional: rtk installed for smaller bash output

Add this badge to your README

Maintain Maki? Show readers where to find these use cases. Use cases on Deduped

Markdown

[![Use cases on Deduped](https://dedupedai.com/badge/tontinton/maki.svg)](https://dedupedai.com/use-cases/tontinton-maki/?utm_source=github&utm_medium=badge&utm_campaign=tontinton-maki)

HTML

<a href="https://dedupedai.com/use-cases/tontinton-maki/?utm_source=github&amp;utm_medium=badge&amp;utm_campaign=tontinton-maki"><img src="https://dedupedai.com/badge/tontinton/maki.svg" alt="Use cases on Deduped" height="20"></a>

A static image, no tracking script. About the badge

Questions about Maki

What is Maki?

maki is a terminal AI coding agent built to use as few context tokens as possible while staying fast and pleasant to use. It parses code with tree-sitter to read file skeletons, runs tools from a sandboxed interpreter, and lets subagents pick a weak, medium or strong model. It is written in Rust with a 60 FPS TUI, Lua plugins like neovim, and supports many providers including Ollama and llama.cpp. It is an open-source project on GitHub: https://github.com/tontinton/maki.

How do I use Maki?

Download the installer with curl -fsSL https://maki.sh/install.sh -o install.sh and read it with cat install.sh; then run it with chmod +x install.sh && sh install.sh, or use brew install maki; set your provider key, for example OPENAI_API_KEY or GEMINI_API_KEY. The use cases on this page give the full steps and a copy-paste agent prompt for each job.

Who is Maki for?

Developers who pay per token or run local models and want a fast coding agent that does not waste context.

What can I do with Maki?

3 use cases so far, for example: Install Maki and cut the tokens your coding agent spends; Run a coding agent on your own Ollama or llama.cpp server; Replace a headless Claude Code script with Maki. Each has steps and a copy-paste agent prompt.

What do I need to run Maki?

Linux, macOS or Windows; An API key or sign-in for a supported provider, or a local Ollama or llama.cpp server; Optional: rtk installed for smaller bash output.

What are alternatives to Maki?

Other hot AI repos in Software and DevOps: ECC, Thinkrail, Superpowers, Deep Infer, Instructor.

Is Maki safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.