Rich text editor, per task

Rich text editor per task. Markdown, nested checklists, code blocks. For when "TODO: figure this out" needs more than a terminal comment.

🏠

PR#24 ×

Auth refactor ×

Search endpoint ×

Rate limiting ×

Auth refactor

▸_ Terminal◧ Browser✎ Editor⎇ Git

✓ JWT middleware rewritten
✓ Token refresh added
src/types/auth.d.ts — updated

Running tests... 14 passed

❯

▾ src/

middleware/

auth.ts

utils/

jwt.ts

types/

auth.d.ts

▾ notes/

plan.md

todo.md

Auth Refactor Plan

Replace session-based authentication with JWT tokens. This affects the middleware layer, token utilities, and all auth-dependent routes.

Checklist

✓

Implement JWT verify utility

✓

Rewrite auth middleware

Update integration tests

Remove session store dependency

Update API documentation

Not every task is best represented as terminal output. Some work needs notes, checkpoints, snippets, or a handoff document that survives past the current session.

The built-in editor gives each task a place for structured context: meeting notes, implementation plans, QA steps, or reminders for the next person touching the branch.

Because it lives on the task, the note stays attached to the work instead of vanishing into a separate docs tool.

Have a question about how this works in practice? Check the SlayZone FAQ or read about all features.

← Previous PRs without the browser Next → Dev servers, managed