Your first task
Watch Jinion take a request from a question to tested code.
To keep the agent's changes away from your own checkout, press ctrl+g before you send the first message. The
conversation then works in a git worktree, on a branch of its own. See Work in parallel with
worktrees.
Type what you want done and press enter:
add rate limiting to the apiJinion looks through the code first. When a choice is yours to make, it asks instead of guessing:
[x] Glob: src/middleware/*.ts 4 files |-- ts src/middleware/index.ts |-- ts src/middleware/cors.ts |-- ts src/middleware/request-id.ts '-- ts src/middleware/error-handler.ts Thought for 6s [-] Waiting for your answer… 0s · esc to interrupt +- Ask 1/3 · storage ----------------------------------------------------------------------+ | Where should the limiter keep its counters? | | | +------------------------------------------------------------------------------------------+ | > 1. In-memory | | single process, zero dependencies | | 2. Redis | | shared across instances, needs REDIS_URL | | 3. In-memory behind a store seam | | Redis can be added later | | 4. Other (type your own) | +------------------------------------------------------------------------------------------+ | Enter select · n note · Up/Down move · Esc cancel | +------------------------------------------------------------------------------------------+
Its thinking shows as it comes, then folds into one line, such as Thought for 6s, once it moves on. ctrl+o expands
it again, with the rest of the output.
Then it edits the files, runs the tests, and fixes what fails. Every edit shows as a diff in the conversation. At the end you get a short summary of what changed and how it was checked.
When the first turn ends, Jinion gives the conversation a title of a few words. It shows on the right of the status
line and in /resume. To give it a title of your own, type /rename and the title. See
Resume a conversation.