Comments URL: https://news.ycombinator.com/item?id=47681107

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47676859

Points: 3

# Comments: 0

I haven't thought much about accessibility, it's not really a priority for the project right now. If the project really gets big I might revisit that. Google docs is canvas-based, so that was enough precedent for me.

this may be something I offer one day, with some kind of one-time license. I can't really make this work without a subscription right now, because it relies on servers I host and LLMs provided by 3rd parties which have metered billing.

I think the way people approach agentic coding depends on their career experience. I had my project acquired previously at the acquiring company hired a large team to work on it. This forced me to go from being a solo dev to a technical manager who's got dozens of people working on code. I treat codex/claude the same way as that; I am leading the ship and it's doing most of the heavy lifting. It's leverage and helps you get more done if you give the right guidance, constraints, and acceptance criteria.

For now, the catch-all solution that anyone can attempt to use is the custom prompt, under account settings. You can instruct it never to use emdash, avoid certain cliches, or simple things like that. But you have to write it yourself for now, there's no convenient presets or anything like that.

If you have ideas please email me art@revise.io

The agent is model-agnostic though; I already have integrations with 3 providers. It could be extended to more free speech friendly models in the future, should there be good ones that can handle tool calls well enough.

You can also focus your questions by selecting a segment of your document, and then writing a prompt; the agent will see what you've selected and focus its efforts on that. You can even prompt with multiple selections attached at once.

I'm hoping to add more "proactive" AI to this eventually, like automatic comments raising the critiques along the lines of these questions you enumerated. Right now the agent has to be prompted first for it to do any real thinking.

Thanks for the feedback.

Notion can't quite format and export print-ready documents the same way. This is more akin to Google Docs than Notion. Revise can do proper word processor esque formatting, like page numbers, page layout, page breaks. The agent can format a paper in APA 7 with a single prompt, for example.

I already have a growing user base and customer base. People use Revise for all sorts of things, from writing stories for pleasure, to processing reports for work.

Notion is an amazing tool, but not focused on the same type of documents that Revise is focused on.

I will get all of these fixed

regarding rendering/text layout, it’s all based on measureText in the Canvas API. the layout engine is my own. documents are made up of “blocks” like lists and paragraphs and each implements its own rendering, cursor movement, and layout logic.

I am going to start a dev blog where I get into the weeds. but will fix these bugs first.

if you find more like that please email me art@revise.io