title: Can't access Heroku console with app name
body: <p>I just started a new app and I was able to push it to Heroku, But I it seems, that I can't access the console.</p>
  
  <p>The command, that I am running is:</p>
  
  <pre><code>heroku run console --app myappname
  </code></pre>
  
  <p>What I get, is:</p>
  
  <pre><code>Running `console` attached to terminal... up, run.3951 Usage:   rails
  new APP_PATH [options]
  
  Options:   -r, [--ruby=PATH]              # Path to the Ruby binary of
  your choice
                                   # Default: /app/vendor/ruby-1.9.3/bin/ruby   -b, [--builder=BUILDER]        #
  Path to a application builder (can be a filesystem path or URL)   -m,
  [--template=TEMPLATE]      # Path to an application template (can be a
  filesystem path or URL)
        [--skip-gemfile]           # Don't create a Gemfile
        [--skip-bundle]            # Don't run bundle install   -G, [--skip-git]               # Skip Git ignores and keeps   -O,
  [--skip-active-record]     # Skip Active Record files   -S,
  [--skip-sprockets]         # Skip Sprockets files   -d,
  [--database=DATABASE]      # Preconfigure for selected database
  (options:
  mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
                                   # Default: sqlite3   -j, [--javascript=JAVASCRIPT]  # Preconfigure for selected JavaScript
  library
                                   # Default: jquery   -J, [--skip-javascript]        # Skip JavaScript files
        [--dev]                    # Setup the application with Gemfile pointing to your Rails checkout
        [--edge]                   # Setup the application with Gemfile pointing to Rails repository   -T, [--skip-test-unit]         # Skip
  Test::Unit files
        [--old-style-hash]         # Force using old style hash (:foo =    'bar') on Ruby &gt;= 1.9
  
  Runtime options:   -f, [--force]    # Overwrite files that already
  exist   -p, [--pretend]  # Run but do not make any changes   -q,
  [--quiet]    # Suppress status output   -s, [--skip]     # Skip files
  that already exist
  
  Rails options:   -h, [--help]     # Show this help message and quit  
  -v, [--version]  # Show Rails version number and quit
  
  Description:
      The 'rails new' command creates a new Rails application with a default
      directory structure and configuration at the path you specify.
  
      You can specify extra command-line arguments to be used every time
      'rails new' runs in the .railsrc configuration file in your home directory.
  
      Note that the arguments specified in the .railsrc file don't affect the
      defaults values shown above in this help message.
  
  Example:
      rails new ~/Code/Ruby/weblog
  
      This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
      See the README in the newly created application to get going.
  </code></pre>
  
  <p>I know, that the application name is correct, as I just pushed it and it is loaded.</p>
  
  <p>When I look at the logs on Heroku for the moment, when I tried to hit the console, I see following:</p>
  
  <pre><code>2013-07-01T16:21:58.780979+00:00 heroku[api]: Starting process with command `bundle exec rails console` by mzaragoza@myemail.com
  2013-07-01T16:22:09.000482+00:00 heroku[run.2993]: Awaiting client
  2013-07-01T16:22:09.055474+00:00 heroku[run.2993]: Starting process with command `bundle exec rails console`
  2013-07-01T16:22:10.342966+00:00 heroku[run.2993]: State changed from starting to up
  2013-07-01T16:22:13.870963+00:00 heroku[run.2993]: Process exited with status 0
  2013-07-01T16:22:13.889703+00:00 heroku[run.2993]: State changed from up to complete
  </code></pre>