AskCodi

Orchestrated AI for developers: a Mac app and an API

3.8•4 reviews•

515 followers

Orchestrated AI for developers: a Mac app and an API

3.8•4 reviews•

515 followers

Visit website

Productivity

•

AI Infrastructure Tools

AskCodi orchestrates AI coding, two ways. Talk to Codi, an AI CTO in the Mac app that runs a team of agents and picks the right model for every job. Or call the same orchestration as an OpenAI-compatible API. Bring your own key. Key features 🤖 BYOK: Claude Code, Codex CLI, and more 🧠 An AI CTO that plans, delegates, and ships 💸 Auto model routing, low cost by default 🗂️ Remembers your whole codebase 🔌 OpenAI-compatible API for any LLM 📊 Analytics and cost controls

This is the 4th launch from AskCodi. View more

AskCodi

Launching today

Orchestrate agents at scale while reducing cost

Tell Codi what you want to build. It writes the plan, runs AI agents in parallel across all your projects, and picks the cheapest model that can do each task, so you ship more and spend less. When you add a project it writes the charter and task list itself, and only pulls you in when a decision needs you, through one inbox.

Free Options

Launch tags:Mac•Productivity•Artificial Intelligence

Launch Team / Built With

Framer AI AgentsDesign and publish professional sites with AI

Promoted

OpenAI

OpenAI Day

How did GPT-5.6 change the ambition or scope of what you shipped?

AskCodi

Maker

AskCodi is model-agnostic, so a jump like GPT-5.6 raises our ceiling directly, and the change was mostly about trust. Before, the models were good enough to demo an autonomous "AI CTO" but not reliable enough to let it run a team unattended, so we kept a human on every step and scoped the product down to stay safe. GPT-5.6 was the point we stopped hedging. Agents could take longer, more autonomous runs and actually come back with usable work, so we shipped the things we'd been too nervous to ship: Codi running in your off-hours, and running several projects in parallel. It also sharpened our core bet on cost. As the frontier gets both smarter and cheaper, routing the boring work to small models and saving the expensive calls for the hard parts saves people even more, so "a fraction of the cost" got stronger, not weaker.

Report

12h ago

AskCodi

Maker

📌

Hi, I'm Shreyans, one of the makers. I built AskCodi because I got tired of babysitting AI. Every tool I tried turned building software into a second job. Pick the model, paste the context, wire up the agents, then sit there watching a run and hoping it didn't go sideways. I was spending more time operating the tool than shipping with it. So we made the opposite of that. You hire Codi, an AI CTO that lives on your Mac, and you talk to it the way you'd talk to a real one. You don't manage a fleet of agents. You manage one person, and that person runs the team. You've probably seen tools that give you a control center for your agents: terminals, panes, worktrees, all of it yours to drive. This is the opposite. I didn't want a bigger cockpit. I wanted to hand the work to someone and step away. A few things I'm proud of, and would love you to poke holes in. Before Codi writes a single line, it sits down and learns the project. It asks what you're building, who it's for, and what it should never touch without checking, then drafts a plan from your answers. So it builds the thing you meant, not the literal words you typed. You never choose a model again. Codi decides task by task. Cheap models for the boring parts, the expensive ones only where they earn it. In our own use, a week of work came out around a dollar, instead of the fifteen-ish it costs to run a frontier model on everything. And it doesn't need you sitting over it. Codi already knows what's next from talking to you, so it keeps working in your off-hours when tokens are cheaper. You close the laptop, it keeps going, and the calls that are actually yours are waiting in an inbox the next morning. That's really the whole product: a chat and an inbox. It also isn't one thing at a time. Codi runs sessions in parallel across every project you have, so you can kick off work on three repos before your coffee is ready and let them all move together. It's the closest I've felt to running a studio on my own. Honest caveat, since I'd rather you hear it from me: it's early. The memory gets sharper the more you use it, and there are rough edges we're still filing down. If you try it, I most want to hear where it annoyed you. One aside: AskCodi also has an OpenAI-compatible API, if you'd rather build on the orchestration than talk to it. The app is what I'm here to show you today, but the same brains are a call away. It's on Mac(Windows coming soon), free to start on your own Claude subscription. Ask me anything, I'll be here all day.

Report

2d ago

zero.xyz

@shreyans_assistiv Congtrats on an awesome launch! Excited to try the new version of AskCodi.

Both routers and sandboxed openclaws are all the rage atm. Seems like you've put them together in a single, inbox-style interface, which seems really cool. But where does it go from here? Can this really become like an AI CTO, that designs your infra, picks the tools, innovates on project concepts, etc?

Report

5h ago

AskCodi

Maker

@daniel_baum We're already moving AskCodi toward becoming a true AI CTO. Instead of managing prompts or implementation details, you communicate with Codi the way a CEO communicates with a CTO: define the vision, explain customer needs, and describe the outcome you want. From there, state-of-the-art LLMs determine the best path to bring that vision to life.

These days, most of what we do is review and approve with a "yes, yes, yes." It's YOLO and tokenmaxxing combined with the efficiency and guardrails of human oversight.

Report

4h ago

@shreyans_assistiv The babysitting line is so real. Love that you went the opposite direction from a bigger cockpit. What happens when two projects need a decision from you at the same time, does the inbox stack them up?

Report

1h ago

AskCodi

Maker

@terminal_candy Yes currently inbox acts exactly as an email inbox. Messages keep stacking up, one idea we has was to let Codi rank them on priority. What do you think about that?

Report

1h ago

@shreyans_assistiv Priority ranking sounds right, as long as the full list stays visible somewhere so nothing waits silently forever. My vote would be to surface whichever decision is blocking the most downstream work first.

Report

21m ago

AskCodi

Maker

@terminal_candy Definitely worth looking into and experimenting more. Thank you for your input!!

Report

10m ago

Flowtica Scribe

💡 Bright idea

Love the “manage one person, not a fleet of agents” framing! Does the inbox only surface blockers, or can I also review the decisions Codi made on its own?

Report

5h ago

AskCodi

Maker

@zaczuo Currently inbox is for blockers but the feature map of each project stores the decision made by codi + every tasks details board also highlights them but they definitely also have a place in the inbox. Thank you for the feedback, definitely going up in the next update.

Report

5h ago

MakersClaw

Maker

@zaczuo this is a good feedback. We agree that important decisions deserve a dedicated view in the inbox too. We’re adding this to an upcoming update, thanks!

Report

5h ago

💎 Pixel perfection

The “I didn’t want a bigger cockpit, I wanted to hand the work to someone and step away” line really captures the problem. a lot of agent tools save time on coding, then quietly create a new job around choosing models, managing context, watching runs, and deciding what happens next. As someone building across multiple parts of a product, the idea of managing one AI CTO instead of babysitting a fleet of agents sounds much closer to the experience I’d actually want :)

The automatic model routing and overnight work are especially interesting, but also where trust matters most. Curious how Codi decides which decisions genuinely need the founder, and what safeguards stop it from confidently moving too far in the wrong direction while nobody is watching?

Report

3h ago

AskCodi

Maker

@andrasczeizel You captured our thought process so well. There are an initial set of ruleset like problems including monetary and security - those are the ones escalated to human. Rest Codi answers as a supervisor. This mainly abstracts the technical decisions away.

The PRs are small enough to do no major harm :)

Report

3h ago

MakersClaw

Maker

@andrasczeizel Codi works against the project charter and feature map it builds with you at the start. That gives it a clear definition of what is in scope, what is out of scope, and what success looks like for each task.

The work also stays contained in isolated git worktrees and produces reviewable diffs. Tests, acceptance criteria, and a separate review pass have to succeed before Codi considers a task complete. If the work changes product scope, introduces a security or spending decision, or conflicts with the original charter, it comes back to you through the inbox.

We want unattended work to mean "useful progress waiting for you," not "surprise, your product changed overnight." Thanks for raising this because that trust boundary is one of the most important parts of what we’re building.

Report

31m ago

Congrats on launching a neat product! QQ: the cost story depends on Codi correctly calling a task 'boring' and handing it to a cheap model, and the tasks that look boring but aren't are exactly where cheap models produce plausible-wrong output. How are solving this conundrum if I didn't invent it at all and it exists?

Report

7h ago

AskCodi

Maker

@artstavenka1 Not boring but suitable. Our algorithm uses public data to see which models perform well for which task. It is about reaping the cost benefit without loosing the accuracy too much. Plus the systems in place (skills and supervisor) boost the accuracy instead of dropping it. It is not a pure llm router, llm just classifies the task as to what kind of task it is and then we choose the best cheapest model for it. Hope that cleared it up a bit.

Report

6h ago

MakersClaw

Maker

@artstavenka1 To add to Shreyans’ answer: routing isn’t a one-way decision. The engineer’s output still has to satisfy the task’s acceptance criteria, tests, and review. If the result exposes unexpected complexity or fails validation, Codi can treat that as evidence that the task was misclassified and escalate it to a more capable model. The savings come from starting efficiently, not from being committed to the first model choice.

Report

5h ago

Even if we clearly explain the full product vision and guidelines to Codi upfront, how do we ensure the AI agents it runs don't drift off course during execution, especially on longer, multi-step tasks? What mechanisms are in place to keep them aligned with the original intent throughout, not just at the start?

Report

9h ago

MakersClaw

Maker

@piyush_bhansali2 The system has been tested to build out complete applications from start and we have seen certain behaviours from agents that is preventing it from drifting

Codi truly acts as a supervisor - reviewing not just the PRs but also the plan
Agents are escalating to human users when some request doesn't align with the vision or user experience
Daily briefings shows what is built and what is left at any given time. Purposefully built to always stay updated of what agent is working on and correct as fast as possible

Agents are problematic in that format but alignment is core of the product we have built.

Report

9h ago

Congrats on the launch guys 🥳! Quick question though I'd usually want to run 2-3 branches on the same repo at once (say a feature, a bugfix, and a refactor in parallel). Does AskCodi isolate that at the branch/worktree level within a single project so they don't conflict, or is the parallelism mainly across separate projects?

Report

9h ago

MakersClaw

Maker

@raunak_bhansali Thanks! 🙌 Great question. Isolation is at the worktree level: each task gets its own branch and git worktree, so a feature, a bug fix, and a refactor never share a working tree or step on each other. Right now Codi runs them isolated and coordinates them rather than firing all three at the exact same instant, and true simultaneous same-repo branches are on the near-term list. Across projects it's already fully parallel.

Report

7h ago

1 2 3

Previous AskCodi Launches

AskCodiCustom LLMs, without training. Use via openai compatible api

Launched on November 26th, 2025

AskCodiUnleash the full power of coding with AI

Launched on September 21st, 2023

AskJarvis.ioYour very own Personal AI code assistant, ask him anything

Launched on November 24th, 2021

AskCodi

Orchestrated AI for developers: a Mac app and an API

Orchestrated AI for developers: a Mac app and an API

AskCodi

Previous AskCodi Launches

Previous AskCodi Launches

What's great

What needs improvement

What's great

What's great

What needs improvement

What's great