<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Lambros Photios</title>
    <description>The latest articles on DEV Community by Lambros Photios (@lambrosphotios).</description>
    <link>https://dev.to/lambrosphotios</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3368699%2F78f1b05f-3f08-45bf-a44a-8b870b7c34db.jpg</url>
      <title>DEV Community: Lambros Photios</title>
      <link>https://dev.to/lambrosphotios</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lambrosphotios"/>
    <language>en</language>
    <item>
      <title>Lovelace - Project management that lives in your repo, built for agents</title>
      <dc:creator>Lambros Photios</dc:creator>
      <pubDate>Thu, 23 Jul 2026 11:18:50 +0000</pubDate>
      <link>https://dev.to/lambrosphotios/lovelace-project-management-that-lives-in-your-repo-built-for-agents-1p6p</link>
      <guid>https://dev.to/lambrosphotios/lovelace-project-management-that-lives-in-your-repo-built-for-agents-1p6p</guid>
      <description>&lt;p&gt;I founded Adaca a decade ago and today we build software with 150+ engineers. Over the past year more and more of that building happens through AI coding agents, and I kept hitting the same wall: the agents work inside the repository, and the project tracker lives somewhere else entirely. Every session meant pasting a ticket into a prompt, letting Claude work, then walking back to the tracker to explain what happened.&lt;/p&gt;

&lt;p&gt;That's how Lovelace was born: a desktop app where tickets, docs, and agent session records are Markdown files inside your repo, and Claude works the same files through MCP.&lt;/p&gt;

&lt;h2&gt;
  
  
  Story to date:
&lt;/h2&gt;

&lt;p&gt;Three weeks ago I pointed Lovelace at its own repository, and it has managed its own development ever since: 139 tickets and 144 agent session records, most of them written by Claude. This week it went public. (If you remember an earlier Lovelace from a previous post of mine, an online IDE: the name survived, the product changed shape.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Features 🔥
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;📋 Kanban board and list view generated from your schema - define your own ticket types, fields and statuses, and the columns, filters and forms follow&lt;/li&gt;
&lt;li&gt;📝 Ticket pages with a block editor and a timeline of the comments, sessions and commits that touched the ticket&lt;/li&gt;
&lt;li&gt;📚 A docs tree in the repo (ADRs, guides, plans) plus a graph of the wiki-links between everything&lt;/li&gt;
&lt;li&gt;🤖 8 MCP tools for Claude, every write validated against your schema&lt;/li&gt;
&lt;li&gt;🧭 Fresh sessions start oriented - a hook injects a ~1,500 token digest of in-progress tickets and recent session records&lt;/li&gt;
&lt;li&gt;🛑 A stop hook makes Claude write a session record before finishing, and a guard hook blocks direct edits to ticket files&lt;/li&gt;
&lt;li&gt;⏱️ Live presence on the board, with an elapsed timer while Claude works&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What makes Lovelace different:
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Files are the source of truth.&lt;/strong&gt; Hand-edit anything and the app re-validates live; a broken file gets you an error with file and line, never a crash.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Local-first, for real.&lt;/strong&gt; No server, no database, no account, no telemetry. The update check is the only network call the app makes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The history is public proof.&lt;/strong&gt; Every ticket and session record that built Lovelace is in the repo, including a bug it filed against itself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Free and open source&lt;/strong&gt; (AGPL-3.0).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Demo 🚀
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9v9yhi3mblwwys4dcnad.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9v9yhi3mblwwys4dcnad.gif" alt="Lovelace demo" width="599" height="354"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Download for macOS, Linux and Windows at &lt;a href="https://lovelace.co" rel="noopener noreferrer"&gt;lovelace.co&lt;/a&gt;, or read everything, tickets included, at &lt;a href="https://github.com/lovelace-co/lovelace" rel="noopener noreferrer"&gt;github.com/lovelace-co/lovelace&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;What should a project remember that your tracker doesn't? I'd love to hear what you'd build into it, thank you :)&lt;/p&gt;

</description>
    </item>
    <item>
      <title>I created Lovelace 💜 - An online AI-enabled IDE for developers who code from anywhere</title>
      <dc:creator>Lambros Photios</dc:creator>
      <pubDate>Tue, 28 Oct 2025 09:57:28 +0000</pubDate>
      <link>https://dev.to/lambrosphotios/i-created-lovelace-an-online-ai-enabled-ide-for-developers-who-code-from-anywhere-864</link>
      <guid>https://dev.to/lambrosphotios/i-created-lovelace-an-online-ai-enabled-ide-for-developers-who-code-from-anywhere-864</guid>
      <description>&lt;p&gt;&lt;strong&gt;Story to date:&lt;/strong&gt; I founded Adaca, a tech consultancy based in Sydney, Australia about 10 years ago, where I now serve as the CTO.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The story behind Lovelace:&lt;/strong&gt; Stepping into the CTO role after years of serving as CEO, I was finally back in the position of building tech rather than scaling the business. That's when I came across Cursor for AI-enabled development. Cursor is a VS Code fork with separate builds for each operating system made with Electron. While that's fine for me, most of our team don't have access to the same level of compute and can't be running multiple instances of Cursor. I wanted to make an AI-enabled IDE that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Runs online&lt;/strong&gt; 🌐&lt;/li&gt;
&lt;li&gt;Has &lt;strong&gt;multi-platform support&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Has &lt;strong&gt;multi-device support&lt;/strong&gt; &lt;/li&gt;
&lt;li&gt;Is &lt;strong&gt;accessible from anywhere&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Is &lt;strong&gt;not another VS Code fork&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's how Lovelace was born. While not an alternative to Cursor (yet), it was born as a minimalist solution that aims to solve these problems. It certainly needs more features and love, which I hope to build with feedback and ideas from developers like you.&lt;/p&gt;

&lt;p&gt;When I checked other platforms, I found them leaning into vibe coding rather than supporting developers. Flashy AI autocomplete that makes you &lt;em&gt;feel&lt;/em&gt; productive, but not much else. But here's what I learned building Adaca: &lt;strong&gt;AI really enables us to code from anywhere.&lt;/strong&gt; Not just autocomplete. Not just chat. Genuine development work. Reviewing PRs on your phone, spinning up a feature branch from your tablet at a client site, debugging production issues from whatever device is nearest.&lt;/p&gt;

&lt;p&gt;That's why I built Lovelace with &lt;strong&gt;pure web technologies&lt;/strong&gt; (TypeScript + Next.js) + modern browser APIs 💜&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Did I mention this is currently free to use?&lt;/strong&gt; Well no, it's not if you jump onto the app. But shoot me a message and I'll gladly add credits to your account once you register.&lt;/p&gt;

&lt;p&gt;The Lovelace IDE helps you code from anywhere, on any device, saving time when you're away from your main development machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Features&lt;/strong&gt; 🔥
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Lightweight browser-based IDE (no Electron bloat)&lt;/li&gt;
&lt;li&gt;AI-powered code completion and generation&lt;/li&gt;
&lt;li&gt;AI Agent for development support&lt;/li&gt;
&lt;li&gt;Multi-file project support&lt;/li&gt;
&lt;li&gt;Cloud-based workspace (code from anywhere)&lt;/li&gt;
&lt;li&gt;GitHub / GitLab / Bitbucket integration&lt;/li&gt;
&lt;li&gt;Responsive design (works on tablets and phones)&lt;/li&gt;
&lt;li&gt;CLI support for local codebase mirroring (in testing)&lt;/li&gt;
&lt;li&gt;In-app deployment to containers (coming soon)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Features planned for the near future:&lt;/strong&gt;
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Enhanced debugging capabilities&lt;/li&gt;
&lt;li&gt;MCP Server marketplace&lt;/li&gt;
&lt;li&gt;Configurable system prompts&lt;/li&gt;
&lt;li&gt;Offline mode with service workers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🎁 &lt;strong&gt;Bonus:&lt;/strong&gt; Lovelace supports both light and dark mode&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;What makes Lovelace different:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'm not trying to replace your main IDE (not that I'd be sad if we did). I'm building for the moments when you &lt;em&gt;can't&lt;/em&gt; use your main IDE. When you're:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reviewing code on your commute&lt;/li&gt;
&lt;li&gt;Making a quick fix from your client's office&lt;/li&gt;
&lt;li&gt;Helping your team debug something urgent while you're on holiday&lt;/li&gt;
&lt;li&gt;Prototyping an idea on your lunch break with just your tablet&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The future of development isn't tied to a single machine. It's distributed, flexible, and happens wherever you are.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;a href="https://lovelace.sh/" rel="noopener noreferrer"&gt;Demo 🚀&lt;/a&gt;
&lt;/h2&gt;

</description>
      <category>programming</category>
      <category>webdev</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
