KARMENKoder
中文 Download

Use

Examples

No examples have been published yet. Here is how one change moves through the app.

Koder, dev view: the sample workspace’s file tree on the left, src/format.js open in the middle, a new task’s chat on the rightKoder, dev view: the sample workspace’s file tree on the left, src/format.js open in the middle, a new task’s chat on the right Workbench home: shortcuts, three first-run steps, project and work counts, and today’s pulseWorkbench home: shortcuts, three first-run steps, project and work counts, and today’s pulse

1 / 2

Screenshots: The dev view has a file from the sample workspace open. The workbench home shows counts of projects and work.

One change, inside the app

  1. Start a task in a folder and write the change you want, for example move the Friday deadline to Thursday and run the tests.
  2. Koder shows a diff for notes/plan.md. It is written only when you click Accept. A rejection is not written to disk.
  3. A command that needs to run is its own card. It asks first by default. The review column keeps files waiting for Accept and commands waiting for Allow.
  4. The workbench home can show this task, the related work, and the next automation. An automation runs only while Koder is open.

What the window looks like is on the window. To do it yourself, see the tutorial.

Walk the window yourself

Start a task, pick one of your folders as the workspace, and type a specific change, for example move the Friday deadline to Thursday. A “wants to edit” card appears in the middle. A red line is what would be removed. A green line is what would be written. Click Reject and the file stays as it is. Click Accept and it is written.

If a command needs to run at the same time, it is its own card. The three buttons are Reject, Always allow, and Allow. Always allow remembers the rule for that one command. A dangerous command still asks every time. The workbench home can then show this task and the related work.