Prostir

Research-backed article

AI coding agent that knows your codebase and rules

An AI coding agent that knows your codebase and rules reads your current repo notes, and you still review every change.

7 days free. No card required.

Before you read

What you get

A coding agent that reads your current repository rules, with a diff, tests and review for every change.

Who it's for

People setting up a private agent for one recurring part of their work or life, with clear limits on data, access and actions.

Topics

AI coding agent · Repository rules · MCP · OAuth

01

Stop rebuilding project context

Developers often come back to a project and rebuild the whole picture in their head. Or they correct an agent on Tuesday and see the same mistake on Friday.

One giant context file goes stale too. Keep a small set of current repository instructions, decisions, examples and test commands, each with an owner and a review date.

02

Make the repository the source

Treat the repository as the main source: tracked AGENTS files, architecture notes, schemas, test commands and examples.

The agent can find and explain that context in supported coding clients. It should never treat its memory as newer than Git.

Update a project rule in the same change as the code that makes it true.

03

Keep knowledge, memory and tools apart

Knowledge holds approved material that lasts. User Memory holds small private preferences. Tools do live lookups or the actions you allow.

A remembered preference can never grant access, publish or delete anything. Sensitive writes need the real user, narrow permissions, a confirmation, history and a way to revoke access.

04

Use one agent in every coding client

Publish one agent and connect it through its MCP endpoint to Cursor, Codex, Claude Code or another client that supports MCP with your account and sign-in.

Prostir hosts the agent that holds your context and tools. It doesn't edit code on your machine. The coding client makes the edits, under its own permissions.

05

Review every change before merge

Ask for a diff, passing tests, and the exact expected and actual output. A person reviews before merge or deployment.

Test typical questions, outdated notes, a refused action and one recovery. Track finished tasks, corrections and the time you spend keeping the rules current.

Grow the setup only after the small version stays accurate.

Solutions

Build your agent from one prompt

Start with one customer question or routine task. Builder sets up the agent with your files and the actions you allow, and Prostir hosts and runs it.

Image preview