ADE

Every AI coding tool.
One app that runs everywhere.

[ADE @ade_app_dev]

@LilithLiJapan @theo an agent editing the app you're using to run the agent is a wild loop. what happens if the change breaks the panel mid-session, is there an easy rollback?

[ADE @ade_app_dev]

@JoseCSancho naming panes by the current job is smart, five identical terminals is chaos. does the name update when the agent drifts into a different subtask mid-run, or is it set from the first prompt?

[ADE @ade_app_dev]

@SrinivasValekar the stepping-on-each-other part is the whole game. separate copy of the repo per agent fixes the file collisions, but merging their work back is where it still gets messy. do any of those 3 help when two agents touch the same file, or is that still manual?

[ADE @ade_app_dev]

@Revolt3r computer name + status were the two things we made sure stay on one line at phone width for exactly that. when you check in, is it mostly "is it waiting on me" or do you actually read diffs on the phone?

[ADE @ade_app_dev]

ade web on a phone, before vs after.

at 390px the computers panel wrapped every name one word per line. now names stay on one line, status gets the full width, buttons sit under.

sidebar turns into a drawer under 720px too.

what do you check from your phone while agents run?

[ADE @ade_app_dev]

@Shoumya23 the useful split is having review, ci fixes, and picking up existing prs as separate skills. which one has saved you the most time so far?

[ADE @ade_app_dev]

@TbYoutuber one worktree per package makes sense for keeping the changes separate. do you run each package’s tests before merging too, or wait for the full suite at the end?

[ADE @ade_app_dev]

@stretchcloud the review bandwidth point feels real; once agents can keep working, the slow bit is deciding what actually needs a human. how do you keep the team review from turning into another queue to babysit?

[ADE @ade_app_dev]

@aGim_asf makes sense; a few points on a leaderboard wouldn’t be enough to change a daily setup. what keeps opus 5.5 in your rotation?

[ADE @ade_app_dev]

if you run a few coding agents on ios at once, each one used to pop its own https://t.co/jQ8UOb49za window onto your screen. in ADE the simulators now stay in the background unless you ask for the window, so your mac stays usable while the agents tap through the app

how many simulators do you usually have going?

[ADE @ade_app_dev]

@aGim_asf 3 points on an index is pretty small, i'd be curious how it holds on real multi-file repo work vs the benchmark tasks. are you switching your daily driver based on this, or sticking with whatever you're used to?

[ADE @ade_app_dev]

@JamesMalsawm the one i hear most is it stays on task through a long multi-file change instead of wandering off. is yours about output quality, or more the tooling around it?

[ADE @ade_app_dev]

@fawadhsdev splitting reviewer from the dev session makes sense, a model grading its own diff is too nice to itself. when the review session pushes back, does the dev one just redo it or do you step in?

[ADE @ade_app_dev]

@jaimefjorge the 'never weaken a test to pass a gate' rule is a good one, agents do that way more than i'd like. do the rules get checked while the agent is working or only when it tries to commit?

[ADE @ade_app_dev]

@carlaconwifi tying a change request to the exact frame beats describing it from memory. do the notes stay lined up after claude cuts a section out?

[ADE @ade_app_dev]

@ayoub_el77927 a bug needs a failing test or a concrete repro, not just another review saying it exists. are the later passes finding real failures or mostly style changes?

[ADE @ade_app_dev]

@josiah_arcanist the grouped merge queue bit is useful. passing alone says nothing about two agents changing the same assumption. when a batch fails, do you bisect it automatically or send the whole failure back to the agents?

[ADE @ade_app_dev]

@dlewis filtering before the result hits context seems like the real win, especially for logs. do you keep the raw output somewhere so the agent can dig back in when a filter hides the clue?

[ADE @ade_app_dev]

@aapakari separate clones make that boundary much clearer. would you bring the commits back with cherry-pick after review, or export a patch?

[ADE @ade_app_dev]

ade's import dialog pulls cli sessions you started outside the app back in so you can keep going. it already found claude and codex runs, now it also picks up droid, grok, kimi and pi sessions you ran on a preset or a routed model. hit continue and it resumes in the same folder with the same settings